Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c6040f53dc24f58371b9e91d2178f277ded1a54fee12646ccd5c817e787ead9

Tx prefix hash: 6d53b23d6d557e0383303c8074828adfda6e7e1690925f5ce7a5dce2425d1ea0
Tx public key: eddfcab479334b1428d0ad00c16d9d79fb5c52c745282a27b81eac29afc9f6e3
Timestamp: 1705485362 Timestamp [UCT]: 2024-01-17 09:56:02 Age [y:d:h:m:s]: 01:152:02:46:06
Block: 937205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369756 RingCT/type: yes/0
Extra: 01eddfcab479334b1428d0ad00c16d9d79fb5c52c745282a27b81eac29afc9f6e302110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c47a17f677b7134ac18a223548a6504f14089967e32ae6bcf21ae8628921f516 0.600000000000 1395249 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": 937215, "vin": [ { "gen": { "height": 937205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c47a17f677b7134ac18a223548a6504f14089967e32ae6bcf21ae8628921f516" } } ], "extra": [ 1, 237, 223, 202, 180, 121, 51, 75, 20, 40, 208, 173, 0, 193, 109, 157, 121, 251, 92, 82, 199, 69, 40, 42, 39, 184, 30, 172, 41, 175, 201, 246, 227, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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