Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16a0e7f61b7595533b7f73867541226ea86a2e80148f7f50ca757080a8d48e68

Tx prefix hash: 4eb6342aefb4a1dc1ae3f934d8223b4d0beecbfe2929c62d576338aa1d771a84
Tx public key: 80ea9191defdb12f73ad1f0e5147573274b0866b33583973ac456628aa63365e
Timestamp: 1744593655 Timestamp [UCT]: 2025-04-14 01:20:55 Age [y:d:h:m:s]: 00:293:18:49:02
Block: 1260966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207595 RingCT/type: yes/0
Extra: 0180ea9191defdb12f73ad1f0e5147573274b0866b33583973ac456628aa63365e0211000000058368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f41c101c06f45678b91e4afe66e9a053acb4e9dbf542057ddc8453cbbc8c540d 0.600000000000 1748131 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": 1260976, "vin": [ { "gen": { "height": 1260966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f41c101c06f45678b91e4afe66e9a053acb4e9dbf542057ddc8453cbbc8c540d" } } ], "extra": [ 1, 128, 234, 145, 145, 222, 253, 177, 47, 115, 173, 31, 14, 81, 71, 87, 50, 116, 176, 134, 107, 51, 88, 57, 115, 172, 69, 102, 40, 170, 99, 54, 94, 2, 17, 0, 0, 0, 5, 131, 104, 38, 109, 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