Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23b1e9563825c284310d43c52295f8f43e21d0f1129902655928af19f7c1aea3

Tx prefix hash: 1e179517eeb6ae213dc3785cef29db0fef0ff1ce3b4bff892567baa3ff88c88b
Tx public key: deb5aa9297588a5e3f15e21335a8becc52129b5ee705ceaffcf0a2e89ca0dfd6
Timestamp: 1657168481 Timestamp [UCT]: 2022-07-07 04:34:41 Age [y:d:h:m:s]: 02:220:19:08:28
Block: 538350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 678920 RingCT/type: yes/0
Extra: 01deb5aa9297588a5e3f15e21335a8becc52129b5ee705ceaffcf0a2e89ca0dfd6021100000006c9067537000000000000000000

1 output(s) for total of 10.097715249000 dcy

stealth address amount amount idx
00: 8b64e6dfde6d3adc7a4dd0d619f94cc7dae4f3c45b3babd9966d1df6bb623876 10.097715249000 968339 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": 538360, "vin": [ { "gen": { "height": 538350 } } ], "vout": [ { "amount": 10097715249, "target": { "key": "8b64e6dfde6d3adc7a4dd0d619f94cc7dae4f3c45b3babd9966d1df6bb623876" } } ], "extra": [ 1, 222, 181, 170, 146, 151, 88, 138, 94, 63, 21, 226, 19, 53, 168, 190, 204, 82, 18, 155, 94, 231, 5, 206, 175, 252, 240, 162, 232, 156, 160, 223, 214, 2, 17, 0, 0, 0, 6, 201, 6, 117, 55, 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