Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d62b5cbbcc94baec87c7d4928d253845576c4f1cdde87f16c4b92543bd4b8269

Tx prefix hash: bad5a5724bc40f6e6bbfe452825baa6f200a0a8466cc43d8007a7a08135304d7
Tx public key: 60b5b7c00731ed3b69d2d77961c4581b7b9789b42de4c3444fd2e1d1d15efdb5
Timestamp: 1740154324 Timestamp [UCT]: 2025-02-21 16:12:04 Age [y:d:h:m:s]: 00:226:09:05:14
Block: 1224164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159511 RingCT/type: yes/0
Extra: 0160b5b7c00731ed3b69d2d77961c4581b7b9789b42de4c3444fd2e1d1d15efdb50211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a276471b2c92744264ad85d83ad54d015252db6e40a7fcda29715b586a75a50c 0.600000000000 1711021 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": 1224174, "vin": [ { "gen": { "height": 1224164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a276471b2c92744264ad85d83ad54d015252db6e40a7fcda29715b586a75a50c" } } ], "extra": [ 1, 96, 181, 183, 192, 7, 49, 237, 59, 105, 210, 215, 121, 97, 196, 88, 27, 123, 151, 137, 180, 45, 228, 195, 68, 79, 210, 225, 209, 209, 94, 253, 181, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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