Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0a8896ef16235ee5b7eac592108c6430bd150746ccd7fc1162e65d61a2845f1

Tx prefix hash: 5a6e05e6c894d1a0d2a1f4a9881578a5470acddd960aa08a5511d77daa1d9a5d
Tx public key: 52befb02bc02e35ec32a34ca908877e96e652217f7a7cf225439b91408385ce4
Timestamp: 1577524919 Timestamp [UCT]: 2019-12-28 09:21:59 Age [y:d:h:m:s]: 05:067:21:25:27
Block: 33326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198454 RingCT/type: yes/0
Extra: 0152befb02bc02e35ec32a34ca908877e96e652217f7a7cf225439b91408385ce40211000000019159db1e000000000000000000

1 output(s) for total of 475.968251697000 dcy

stealth address amount amount idx
00: 8cf67e4ca728603d284d00c88abd5563e8cc5509e37a335af3b752b3c68f581f 475.968251697000 55778 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": 33336, "vin": [ { "gen": { "height": 33326 } } ], "vout": [ { "amount": 475968251697, "target": { "key": "8cf67e4ca728603d284d00c88abd5563e8cc5509e37a335af3b752b3c68f581f" } } ], "extra": [ 1, 82, 190, 251, 2, 188, 2, 227, 94, 195, 42, 52, 202, 144, 136, 119, 233, 110, 101, 34, 23, 247, 167, 207, 34, 84, 57, 185, 20, 8, 56, 92, 228, 2, 17, 0, 0, 0, 1, 145, 89, 219, 30, 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