Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67b6a0971522b1d8e48915c7ac8e90abb5b571357c20c027995e55531252fe5b

Tx prefix hash: bc20cabb0e350df00fb0262df64b35b00d54036023a88439b124f1c797f306ba
Tx public key: 61b7ee8d5c6d160158bdca76f844b34c5e031ea1d921425d6ed0f608e33ff23d
Timestamp: 1713112870 Timestamp [UCT]: 2024-04-14 16:41:10 Age [y:d:h:m:s]: 00:316:14:32:04
Block: 1000434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226338 RingCT/type: yes/0
Extra: 0161b7ee8d5c6d160158bdca76f844b34c5e031ea1d921425d6ed0f608e33ff23d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61d625e26a6d6821d456badff013cec794b995a7e5acb539b8b6fcc92b82fa60 0.600000000000 1460932 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": 1000444, "vin": [ { "gen": { "height": 1000434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61d625e26a6d6821d456badff013cec794b995a7e5acb539b8b6fcc92b82fa60" } } ], "extra": [ 1, 97, 183, 238, 141, 92, 109, 22, 1, 88, 189, 202, 118, 248, 68, 179, 76, 94, 3, 30, 161, 217, 33, 66, 93, 110, 208, 246, 8, 227, 63, 242, 61, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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