Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c213c5109250884374b5b2e1226514e073a8cad903ddc7f0bf1473feeaa6e5b5

Tx prefix hash: 499933903cd5fa891c41e9b2f04057f77006367ce8fc931e0ed6cb10497d0906
Tx public key: 42324f66731e3527f8eea73cbf968e3478d887a33f051d1da45bab24a7f7ab37
Timestamp: 1711524351 Timestamp [UCT]: 2024-03-27 07:25:51 Age [y:d:h:m:s]: 01:064:20:41:39
Block: 987318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307345 RingCT/type: yes/0
Extra: 0142324f66731e3527f8eea73cbf968e3478d887a33f051d1da45bab24a7f7ab370211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b882058ec14ac14dcd60e2e9ef3f2698af8ce9e8f3d98e4e272ed0841640e806 0.600000000000 1447559 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": 987328, "vin": [ { "gen": { "height": 987318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b882058ec14ac14dcd60e2e9ef3f2698af8ce9e8f3d98e4e272ed0841640e806" } } ], "extra": [ 1, 66, 50, 79, 102, 115, 30, 53, 39, 248, 238, 167, 60, 191, 150, 142, 52, 120, 216, 135, 163, 63, 5, 29, 29, 164, 91, 171, 36, 167, 247, 171, 55, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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