Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8483c93722b3b1438b94d4efa4d9adb4a2d204d8e8a169fbb21d65a37d3d8d5d

Tx prefix hash: 81a631ab20ca20d1c26737aac5e006413099bf787818f18096f269ee01cbad7e
Tx public key: dc7a9bee95eec29a8c0c12722d09b24c0a8596e4657838f877a21ac70c417c2f
Timestamp: 1627731931 Timestamp [UCT]: 2021-07-31 11:45:31 Age [y:d:h:m:s]: 03:098:09:16:28
Block: 304482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 842849 RingCT/type: yes/0
Extra: 01dc7a9bee95eec29a8c0c12722d09b24c0a8596e4657838f877a21ac70c417c2f02110000001337cb3088000000000000000000

1 output(s) for total of 60.134710071000 dcy

stealth address amount amount idx
00: f05812b0fef5d034869e24a6dc4d0ec6f6fb4ea4196f5b7951badc606cd08837 60.134710071000 635285 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": 304492, "vin": [ { "gen": { "height": 304482 } } ], "vout": [ { "amount": 60134710071, "target": { "key": "f05812b0fef5d034869e24a6dc4d0ec6f6fb4ea4196f5b7951badc606cd08837" } } ], "extra": [ 1, 220, 122, 155, 238, 149, 238, 194, 154, 140, 12, 18, 114, 45, 9, 178, 76, 10, 133, 150, 228, 101, 120, 56, 248, 119, 162, 26, 199, 12, 65, 124, 47, 2, 17, 0, 0, 0, 19, 55, 203, 48, 136, 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