Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44e932f48ce373488a27aa5ffc6cad44189751ca477911b01c9cc12649d12156

Tx prefix hash: ead4f5902c5f0c85ef65bb2b9443a0a9f59dca094aabc735013bf724b88af917
Tx public key: 0ab7e2fab882d13f58431a398e117b09c4d5149d77aeaea0a393d77a8de1114b
Timestamp: 1730973864 Timestamp [UCT]: 2024-11-07 10:04:24 Age [y:d:h:m:s]: 00:016:17:33:38
Block: 1148449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11974 RingCT/type: yes/0
Extra: 010ab7e2fab882d13f58431a398e117b09c4d5149d77aeaea0a393d77a8de1114b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53d71b8e57bfc3c56ebf2f07ff93dde65420b26921fc969b7c26aadfc61f2f93 0.600000000000 1633292 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": 1148459, "vin": [ { "gen": { "height": 1148449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53d71b8e57bfc3c56ebf2f07ff93dde65420b26921fc969b7c26aadfc61f2f93" } } ], "extra": [ 1, 10, 183, 226, 250, 184, 130, 209, 63, 88, 67, 26, 57, 142, 17, 123, 9, 196, 213, 20, 157, 119, 174, 174, 160, 163, 147, 215, 122, 141, 225, 17, 75, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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