Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfb15c043f7edb88cac33acfd8502aabffa1108401da76c9ca23b2b90b492d1a

Tx prefix hash: 6eb9e77d4d5d747562b27f6401c42eb14e021db23c3bcdeb691b6ee86f08a83f
Tx public key: 15cb37264ea33d3e38d36e454d68feb0b8672caef83b997c93f25b9ebcbd10c6
Timestamp: 1736502923 Timestamp [UCT]: 2025-01-10 09:55:23 Age [y:d:h:m:s]: 00:110:20:26:18
Block: 1194226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79022 RingCT/type: yes/0
Extra: 0115cb37264ea33d3e38d36e454d68feb0b8672caef83b997c93f25b9ebcbd10c60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bbb79623801de75a5b3a8b03cccbd6f683ac68315b5dbef5da10b1c8c7ad765 0.600000000000 1680793 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": 1194236, "vin": [ { "gen": { "height": 1194226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bbb79623801de75a5b3a8b03cccbd6f683ac68315b5dbef5da10b1c8c7ad765" } } ], "extra": [ 1, 21, 203, 55, 38, 78, 163, 61, 62, 56, 211, 110, 69, 77, 104, 254, 176, 184, 103, 44, 174, 248, 59, 153, 124, 147, 242, 91, 158, 188, 189, 16, 198, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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