Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b2eb20811f14cf0468d92f1a8e1fbd71d49b6d6b197f4243846bede1e8d89b

Tx prefix hash: 073348455eefa34de79b33096701df5626e0d080cbf4090a69b275d64a18f589
Tx public key: 8b4f8018a609a4a8af07045dc74e1f268f1c09814d74a00ea5b9f3bef4d3d5aa
Timestamp: 1735111122 Timestamp [UCT]: 2024-12-25 07:18:42 Age [y:d:h:m:s]: 00:102:19:32:09
Block: 1182728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73237 RingCT/type: yes/0
Extra: 018b4f8018a609a4a8af07045dc74e1f268f1c09814d74a00ea5b9f3bef4d3d5aa021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc4089ae1fe4da820877f4c1654d0b22772f6326179ae9769b18036356662b5d 0.600000000000 1669165 of 15

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": 1182738, "vin": [ { "gen": { "height": 1182728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc4089ae1fe4da820877f4c1654d0b22772f6326179ae9769b18036356662b5d" } } ], "extra": [ 1, 139, 79, 128, 24, 166, 9, 164, 168, 175, 7, 4, 93, 199, 78, 31, 38, 143, 28, 9, 129, 77, 116, 160, 14, 165, 185, 243, 190, 244, 211, 213, 170, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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