Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ab9ed934ff208f4ca3039e6c941396f6b231458d6ee831cba8b94a3d8f0539

Tx prefix hash: bc501344fae6c13246b99db25c72aa59eed24ed915d42e1181b96c5132d6cfae
Tx public key: 6cddc09d167635ebaa728f689a2589f8e677fafc7256fdaaeb2c5d4e9d07f08e
Timestamp: 1703093639 Timestamp [UCT]: 2023-12-20 17:33:59 Age [y:d:h:m:s]: 01:336:04:22:36
Block: 917413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499105 RingCT/type: yes/0
Extra: 016cddc09d167635ebaa728f689a2589f8e677fafc7256fdaaeb2c5d4e9d07f08e021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a25fa239ae5b41a686220a4846588c84e3bb9d2a19c0bdc0352255bc6531ecd1 0.600000000000 1374989 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": 917423, "vin": [ { "gen": { "height": 917413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a25fa239ae5b41a686220a4846588c84e3bb9d2a19c0bdc0352255bc6531ecd1" } } ], "extra": [ 1, 108, 221, 192, 157, 22, 118, 53, 235, 170, 114, 143, 104, 154, 37, 137, 248, 230, 119, 250, 252, 114, 86, 253, 170, 235, 44, 93, 78, 157, 7, 240, 142, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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