Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b37ce34b011b740e281c85687b797e144f29f376273a9e9af0acdea64e2dda

Tx prefix hash: 221e2fd467514290dcbb8f730dabaa02f8a8c95a471ac7e981368c3cdfd52b1a
Tx public key: c76c7b009de8e83b7e4a9510ebcff659d9b1c62bee83253c82ae08a3ad31f139
Timestamp: 1763022926 Timestamp [UCT]: 2025-11-13 08:35:26 Age [y:d:h:m:s]: 00:053:15:42:56
Block: 1411114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38434 RingCT/type: yes/0
Extra: 01c76c7b009de8e83b7e4a9510ebcff659d9b1c62bee83253c82ae08a3ad31f13902110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9b9754d5251b6af6601b45864a11d0e8109aeb1b669d6df374b47ae783cf370 0.600000000000 1899571 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": 1411124, "vin": [ { "gen": { "height": 1411114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9b9754d5251b6af6601b45864a11d0e8109aeb1b669d6df374b47ae783cf370" } } ], "extra": [ 1, 199, 108, 123, 0, 157, 232, 232, 59, 126, 74, 149, 16, 235, 207, 246, 89, 217, 177, 198, 43, 238, 131, 37, 60, 130, 174, 8, 163, 173, 49, 241, 57, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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