Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21da023b5f62fa4a4771d49981ffb3c3e7ba67848e4c800a1e2ce9e488b911cc

Tx prefix hash: d9c74d1647a487027c1800f48a856134a5dc4c1274f641dbad71799749e833a7
Tx public key: 2ac9588308843fe1654f480607993e8cbdb3d91d5f99f88e9ba1423c21e6733f
Timestamp: 1736897945 Timestamp [UCT]: 2025-01-14 23:39:05 Age [y:d:h:m:s]: 00:153:09:54:29
Block: 1197496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109362 RingCT/type: yes/0
Extra: 012ac9588308843fe1654f480607993e8cbdb3d91d5f99f88e9ba1423c21e6733f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07d4b5bded2e48e51f59d98392c570d145e1fdde6e7d29275994ce039645be9d 0.600000000000 1684105 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": 1197506, "vin": [ { "gen": { "height": 1197496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07d4b5bded2e48e51f59d98392c570d145e1fdde6e7d29275994ce039645be9d" } } ], "extra": [ 1, 42, 201, 88, 131, 8, 132, 63, 225, 101, 79, 72, 6, 7, 153, 62, 140, 189, 179, 217, 29, 95, 153, 248, 142, 155, 161, 66, 60, 33, 230, 115, 63, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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