Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ccd248646b5a69aa3748a7c62617c24ec8c6188e12737e80a17489e577ffee84

Tx prefix hash: c7a6505e65bdd0e1cd8c788194b7dc59d47bb5fd55c4a0a3e5ea49f81c63c6b6
Tx public key: 988e6d0bfac55379f98b763878cb668a03ca1b2fe4bba0454bb78e7aeb3d4488
Timestamp: 1728706832 Timestamp [UCT]: 2024-10-12 04:20:32 Age [y:d:h:m:s]: 01:032:09:22:45
Block: 1129757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281506 RingCT/type: yes/0
Extra: 01988e6d0bfac55379f98b763878cb668a03ca1b2fe4bba0454bb78e7aeb3d4488021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8f6454888f7fa91c25c7cc3796177c69bce745cee446d3e4380c269208595bf 0.600000000000 1612610 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1129767, "vin": [ { "gen": { "height": 1129757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8f6454888f7fa91c25c7cc3796177c69bce745cee446d3e4380c269208595bf" } } ], "extra": [ 1, 152, 142, 109, 11, 250, 197, 83, 121, 249, 139, 118, 56, 120, 203, 102, 138, 3, 202, 27, 47, 228, 187, 160, 69, 75, 183, 142, 122, 235, 61, 68, 136, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8