Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ded74c944a07f7e3404b3e7735387810e1222b19534b0473daf915df8042b418

Tx prefix hash: 2ddf575731c8e9e5dbff8046be81752e7fbf103d2cc6b2601cc8ce1c76c4500f
Tx public key: eefb9c5ae694b66649cdd4675eafdad8c61ffe7ea382ba0e80340a9dcca4dd92
Timestamp: 1751075226 Timestamp [UCT]: 2025-06-28 01:47:06 Age [y:d:h:m:s]: 00:141:00:41:04
Block: 1314208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98871 RingCT/type: yes/0
Extra: 01eefb9c5ae694b66649cdd4675eafdad8c61ffe7ea382ba0e80340a9dcca4dd92021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb40e24992d1e1f4c78e6612deae7525a081012da1209915f64e909d118c345f 0.600000000000 1801853 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": 1314218, "vin": [ { "gen": { "height": 1314208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb40e24992d1e1f4c78e6612deae7525a081012da1209915f64e909d118c345f" } } ], "extra": [ 1, 238, 251, 156, 90, 230, 148, 182, 102, 73, 205, 212, 103, 94, 175, 218, 216, 198, 31, 254, 126, 163, 130, 186, 14, 128, 52, 10, 157, 204, 164, 221, 146, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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