Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec227eb8b8ea29408ca959ebdeed93b25ded4cd03cfafed397976c7117c655e2

Tx prefix hash: e9b61138ca176fd763b3c36cacc3e5e8673482cf047e474a03cc315b3cf6775c
Tx public key: 8efb931a57d9fe594f455198e94272224022ec25ee8ff6fe0e7e2f53b1d7e7b8
Timestamp: 1744098360 Timestamp [UCT]: 2025-04-08 07:46:00 Age [y:d:h:m:s]: 00:267:11:38:45
Block: 1256834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188973 RingCT/type: yes/0
Extra: 018efb931a57d9fe594f455198e94272224022ec25ee8ff6fe0e7e2f53b1d7e7b80211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e81e10159c3d51e0b39efda868bba209c953f9b50ac5aa37f78a90a99b0d3430 0.600000000000 1743951 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": 1256844, "vin": [ { "gen": { "height": 1256834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e81e10159c3d51e0b39efda868bba209c953f9b50ac5aa37f78a90a99b0d3430" } } ], "extra": [ 1, 142, 251, 147, 26, 87, 217, 254, 89, 79, 69, 81, 152, 233, 66, 114, 34, 64, 34, 236, 37, 238, 143, 246, 254, 14, 126, 47, 83, 177, 215, 231, 184, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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