Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8752df2b30c2bb7ae86308f6ee3666b9792044f011e65d8dd11bd0391d4d367

Tx prefix hash: e51eab0feec0be2d652927f8daa482b2d99450cd4be95cadcd34f9635a68129d
Tx public key: a3ab209d53af561fd477f6578bce4a59af2978d01c1dec5c058906c42e5c9382
Timestamp: 1672680722 Timestamp [UCT]: 2023-01-02 17:32:02 Age [y:d:h:m:s]: 01:334:21:05:15
Block: 666123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500355 RingCT/type: yes/0
Extra: 01a3ab209d53af561fd477f6578bce4a59af2978d01c1dec5c058906c42e5c938202110000000352542ceb000000000000000000

1 output(s) for total of 3.809411979000 dcy

stealth address amount amount idx
00: 5c139d581e802c43642a84181e6653853086ea9fb9b0d4df9713e75c94e364d9 3.809411979000 1107218 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": 666133, "vin": [ { "gen": { "height": 666123 } } ], "vout": [ { "amount": 3809411979, "target": { "key": "5c139d581e802c43642a84181e6653853086ea9fb9b0d4df9713e75c94e364d9" } } ], "extra": [ 1, 163, 171, 32, 157, 83, 175, 86, 31, 212, 119, 246, 87, 139, 206, 74, 89, 175, 41, 120, 208, 28, 29, 236, 92, 5, 137, 6, 196, 46, 92, 147, 130, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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