Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 678480d544d9c89008d8f1f10af9c3c1288941668c050dc6d13af7a2199bc7ea

Tx prefix hash: d083bf3e09906dc8fa1fcf575ed75f2c95d2430e701b6a23a9fc5a6daa5a5c88
Tx public key: b1f9019e6c009e8a31ad4e8a6e3c477ccb38efb59bf3e50b62a06e8ea8a05175
Timestamp: 1713446162 Timestamp [UCT]: 2024-04-18 13:16:02 Age [y:d:h:m:s]: 00:363:18:32:44
Block: 1003203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260076 RingCT/type: yes/0
Extra: 01b1f9019e6c009e8a31ad4e8a6e3c477ccb38efb59bf3e50b62a06e8ea8a051750211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 809dbd6fb89f86e68cd722adfbbd279a5cf3d3d53ceb1ddffd9b294334e08201 0.600000000000 1463733 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": 1003213, "vin": [ { "gen": { "height": 1003203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "809dbd6fb89f86e68cd722adfbbd279a5cf3d3d53ceb1ddffd9b294334e08201" } } ], "extra": [ 1, 177, 249, 1, 158, 108, 0, 158, 138, 49, 173, 78, 138, 110, 60, 71, 124, 203, 56, 239, 181, 155, 243, 229, 11, 98, 160, 110, 142, 168, 160, 81, 117, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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