Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 867a622281af68b00ed05e6853ce584d4c0ccc4b6c4cff15ed6cd85e916385ff

Tx prefix hash: 88170f83d255de23401da78e2aa152495881b7fe9461c1d6d566303f579da77f
Tx public key: 6d92e41cc5a356e8ed99da82e2d7b79b656fb8e8a4a6ec95ff3adf7dcd9d55eb
Timestamp: 1669570922 Timestamp [UCT]: 2022-11-27 17:42:02 Age [y:d:h:m:s]: 02:165:23:42:24
Block: 640371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 640365 RingCT/type: yes/0
Extra: 016d92e41cc5a356e8ed99da82e2d7b79b656fb8e8a4a6ec95ff3adf7dcd9d55eb0211000000015029cbac000000000000000000

1 output(s) for total of 4.636444303000 dcy

stealth address amount amount idx
00: 79a5024e2e6c9819a5667037559ae657a818486fa80e72d2aaf265b652935a82 4.636444303000 1080102 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": 640381, "vin": [ { "gen": { "height": 640371 } } ], "vout": [ { "amount": 4636444303, "target": { "key": "79a5024e2e6c9819a5667037559ae657a818486fa80e72d2aaf265b652935a82" } } ], "extra": [ 1, 109, 146, 228, 28, 197, 163, 86, 232, 237, 153, 218, 130, 226, 215, 183, 155, 101, 111, 184, 232, 164, 166, 236, 149, 255, 58, 223, 125, 205, 157, 85, 235, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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