Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e3b1896b114c9feb71ffb1aeacefb9aad41dcc148bad090bdd8e14fc0e06d9

Tx prefix hash: d4a49dc39967cfaf39fe43cdb8d1dd7871473bcddbc4abc88acb90b33900ee1d
Tx public key: 8839f8636acf3d8cb5785b80f997676ec06ee1aa4585eef623c6c73a6951a3bb
Timestamp: 1700493587 Timestamp [UCT]: 2023-11-20 15:19:47 Age [y:d:h:m:s]: 01:353:00:37:01
Block: 895835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511197 RingCT/type: yes/0
Extra: 018839f8636acf3d8cb5785b80f997676ec06ee1aa4585eef623c6c73a6951a3bb021100000005679a8a81000000000000000000

1 output(s) for total of 0.660277891000 dcy

stealth address amount amount idx
00: fe8a3fc398ea78210446d4c7e042e5ab803ca50e4d788a2815a69408e792b6d9 0.660277891000 1352082 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": 895845, "vin": [ { "gen": { "height": 895835 } } ], "vout": [ { "amount": 660277891, "target": { "key": "fe8a3fc398ea78210446d4c7e042e5ab803ca50e4d788a2815a69408e792b6d9" } } ], "extra": [ 1, 136, 57, 248, 99, 106, 207, 61, 140, 181, 120, 91, 128, 249, 151, 103, 110, 192, 110, 225, 170, 69, 133, 238, 246, 35, 198, 199, 58, 105, 81, 163, 187, 2, 17, 0, 0, 0, 5, 103, 154, 138, 129, 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