Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b02b9d63390e2fbd27e0babb5143caeb03a845a50aa1a0b25f808ae5701eaf6c

Tx prefix hash: 74763b4614b6b5e2595784e1bceef9ccd6c0f74857546cb6274eccdd40436e5a
Tx public key: dc2a7e4ce0a5ef18c7fb7b4cb106d07aba9f38b70cad4509f7d35439da2a2116
Timestamp: 1745524549 Timestamp [UCT]: 2025-04-24 19:55:49 Age [y:d:h:m:s]: 00:011:17:05:47
Block: 1268655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8380 RingCT/type: yes/0
Extra: 01dc2a7e4ce0a5ef18c7fb7b4cb106d07aba9f38b70cad4509f7d35439da2a2116021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 514d0f4367b0622c405f0b0225f005933e6fd5d89c72cfd680ef5604986e7f56 0.600000000000 1755886 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": 1268665, "vin": [ { "gen": { "height": 1268655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "514d0f4367b0622c405f0b0225f005933e6fd5d89c72cfd680ef5604986e7f56" } } ], "extra": [ 1, 220, 42, 126, 76, 224, 165, 239, 24, 199, 251, 123, 76, 177, 6, 208, 122, 186, 159, 56, 183, 12, 173, 69, 9, 247, 211, 84, 57, 218, 42, 33, 22, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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