Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 383b86f0a9f01d04033447fdd6575b951e0bf080ec33eca24fb0d455afd698e3

Tx prefix hash: 773cbe1f94a82b31aa68dc5e4835db8482a268448d5753a5a73b9d33fb6d0f9f
Tx public key: 781e801041e57bd0f862e2ff650551d32a0d8d06de84d4ae60bde490845ae988
Timestamp: 1619874675 Timestamp [UCT]: 2021-05-01 13:11:15 Age [y:d:h:m:s]: 03:351:22:39:37
Block: 251716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1011685 RingCT/type: yes/0
Extra: 01781e801041e57bd0f862e2ff650551d32a0d8d06de84d4ae60bde490845ae9880211000000469e0b6356000000000000000000

1 output(s) for total of 89.941671939000 dcy

stealth address amount amount idx
00: 622ab774c7f2de7843dd36c798f064a5a6fdf2e99df9a428804f878169fb0a01 89.941671939000 528147 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": 251726, "vin": [ { "gen": { "height": 251716 } } ], "vout": [ { "amount": 89941671939, "target": { "key": "622ab774c7f2de7843dd36c798f064a5a6fdf2e99df9a428804f878169fb0a01" } } ], "extra": [ 1, 120, 30, 128, 16, 65, 229, 123, 208, 248, 98, 226, 255, 101, 5, 81, 211, 42, 13, 141, 6, 222, 132, 212, 174, 96, 189, 228, 144, 132, 90, 233, 136, 2, 17, 0, 0, 0, 70, 158, 11, 99, 86, 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