Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6002e14cd5650b996d039195b371e510796b11dfe48d5ef9ab6cd0a2ad1a2fd

Tx prefix hash: 972dbbe7e42ad340f0bf7abf559a11d0ae60be3914048516a89579b19051be72
Tx public key: 0d40e249e9e3e111235bec8ed01b9252d66ada00bf88b26f21976bc6aeba851b
Timestamp: 1696098219 Timestamp [UCT]: 2023-09-30 18:23:39 Age [y:d:h:m:s]: 01:198:10:22:43
Block: 859601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402872 RingCT/type: yes/0
Extra: 010d40e249e9e3e111235bec8ed01b9252d66ada00bf88b26f21976bc6aeba851b0211000000064b8f5122000000000000000000

1 output(s) for total of 0.870532706000 dcy

stealth address amount amount idx
00: 11dd3d8ff1437bc7af647c1472432835e1b64062ad5dc0d094a4a24d2f0f2b9f 0.870532706000 1313835 of 0

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": 859611, "vin": [ { "gen": { "height": 859601 } } ], "vout": [ { "amount": 870532706, "target": { "key": "11dd3d8ff1437bc7af647c1472432835e1b64062ad5dc0d094a4a24d2f0f2b9f" } } ], "extra": [ 1, 13, 64, 226, 73, 233, 227, 225, 17, 35, 91, 236, 142, 208, 27, 146, 82, 214, 106, 218, 0, 191, 136, 178, 111, 33, 151, 107, 198, 174, 186, 133, 27, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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