Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d4efcf7c7342603cadb8a8cab05b37d1eeed1c59d4be3ef9fe47e6994ed023c

Tx prefix hash: 818a00ed3d484c542f83da1e1bd2a8e334512bc35006d646bf47438f1edbd4b9
Tx public key: 812993465bf7aaf503c8c862a6d4aa7b5e5b9f779ab3d711e2d09917818d4443
Timestamp: 1660455574 Timestamp [UCT]: 2022-08-14 05:39:34 Age [y:d:h:m:s]: 02:234:12:38:45
Block: 565456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 688838 RingCT/type: yes/0
Extra: 01812993465bf7aaf503c8c862a6d4aa7b5e5b9f779ab3d711e2d09917818d4443021100000001ec6d1a1a000000000000000000

1 output(s) for total of 8.211257086000 dcy

stealth address amount amount idx
00: 92b9d11f7ffed1eb0fe0c9927abe4c7a835e33d4bbc2694ab3d976a7b6942e07 8.211257086000 998358 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": 565466, "vin": [ { "gen": { "height": 565456 } } ], "vout": [ { "amount": 8211257086, "target": { "key": "92b9d11f7ffed1eb0fe0c9927abe4c7a835e33d4bbc2694ab3d976a7b6942e07" } } ], "extra": [ 1, 129, 41, 147, 70, 91, 247, 170, 245, 3, 200, 200, 98, 166, 212, 170, 123, 94, 91, 159, 119, 154, 179, 215, 17, 226, 208, 153, 23, 129, 141, 68, 67, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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