Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91bebfc28637f2599a9b96f4650e7569c697406b4bf49ce13ad859535b6f6f79

Tx prefix hash: 9befb041556d4e6d75dd0dc45defbd67cbe89fc911f1429a64d34f49af82a198
Tx public key: f4c9d4b75291111bf07b0b121a80e1dcbd4e7bdf776c132d17470b19cc376c4b
Timestamp: 1752382545 Timestamp [UCT]: 2025-07-13 04:55:45 Age [y:d:h:m:s]: 00:120:14:49:57
Block: 1324373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84925 RingCT/type: yes/0
Extra: 01f4c9d4b75291111bf07b0b121a80e1dcbd4e7bdf776c132d17470b19cc376c4b021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a7502ab82d5051ac65aa1506aadc9cf10b1ffabf04c09803a41683e21b5e03 0.600000000000 1812116 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": 1324383, "vin": [ { "gen": { "height": 1324373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a7502ab82d5051ac65aa1506aadc9cf10b1ffabf04c09803a41683e21b5e03" } } ], "extra": [ 1, 244, 201, 212, 183, 82, 145, 17, 27, 240, 123, 11, 18, 26, 128, 225, 220, 189, 78, 123, 223, 119, 108, 19, 45, 23, 71, 11, 25, 204, 55, 108, 75, 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