Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec78b1e32eec49ded5daf63d7831ec45a81a668c0c61bd14088c5df782dd0602

Tx prefix hash: ce6e5549b3f2cc393eb6c20ba543f155f3027e1eca0d9d995f4485a50e0883f6
Tx public key: 0e5b4dd1bc8af7a2e958d309740cd7a3926478bc7e7cf3b6e62b1e168ac002e0
Timestamp: 1749354904 Timestamp [UCT]: 2025-06-08 03:55:04 Age [y:d:h:m:s]: 00:165:02:55:50
Block: 1300367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115699 RingCT/type: yes/0
Extra: 010e5b4dd1bc8af7a2e958d309740cd7a3926478bc7e7cf3b6e62b1e168ac002e002110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e78a8138c96ebf1088deb78c0e5916fe0cb5afa5235f6fdbf8783f59b146bf05 0.600000000000 1787916 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": 1300377, "vin": [ { "gen": { "height": 1300367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e78a8138c96ebf1088deb78c0e5916fe0cb5afa5235f6fdbf8783f59b146bf05" } } ], "extra": [ 1, 14, 91, 77, 209, 188, 138, 247, 162, 233, 88, 211, 9, 116, 12, 215, 163, 146, 100, 120, 188, 126, 124, 243, 182, 230, 43, 30, 22, 138, 192, 2, 224, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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