Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b218da7d362861f4e1ca56d3ebe7e882eff4ece897c05512fa140da7073c17ae

Tx prefix hash: e12eb1c236a13a2c6f5419acc6abf9a5acbdff47672d44605f6d6b4f80bdae58
Tx public key: 16c16eb8a0dbc7be40eb771993ccd98b08fcbbc31253d372d8a8f0823d7ce833
Timestamp: 1760977514 Timestamp [UCT]: 2025-10-20 16:25:14 Age [y:d:h:m:s]: 00:073:03:58:55
Block: 1394184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52373 RingCT/type: yes/0
Extra: 0116c16eb8a0dbc7be40eb771993ccd98b08fcbbc31253d372d8a8f0823d7ce8330211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6396a0f04d18a32f5537dbcc31911bc2313b63d998d2b28fdf585253505540c5 0.600000000000 1882451 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": 1394194, "vin": [ { "gen": { "height": 1394184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6396a0f04d18a32f5537dbcc31911bc2313b63d998d2b28fdf585253505540c5" } } ], "extra": [ 1, 22, 193, 110, 184, 160, 219, 199, 190, 64, 235, 119, 25, 147, 204, 217, 139, 8, 252, 187, 195, 18, 83, 211, 114, 216, 168, 240, 130, 61, 124, 232, 51, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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