Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adf7df1bf059cb40d703192828fa3da1aef9263825b7e6b5f1ca74dca40c414c

Tx prefix hash: 85727248d047ba8f2a9ab4e2af789f13dcd35c3e91214b54715be7811aff0389
Tx public key: bfea8c4488043c86b7085d9d9760332a12037b23b584d4bec1d075fbc31c309c
Timestamp: 1737201636 Timestamp [UCT]: 2025-01-18 12:00:36 Age [y:d:h:m:s]: 00:151:13:59:07
Block: 1200012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108024 RingCT/type: yes/0
Extra: 01bfea8c4488043c86b7085d9d9760332a12037b23b584d4bec1d075fbc31c309c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0cae9d752580274673fc60f6a1af7e9e3200d466f0b4a4facd50170e88681dd 0.600000000000 1686653 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": 1200022, "vin": [ { "gen": { "height": 1200012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0cae9d752580274673fc60f6a1af7e9e3200d466f0b4a4facd50170e88681dd" } } ], "extra": [ 1, 191, 234, 140, 68, 136, 4, 60, 134, 183, 8, 93, 157, 151, 96, 51, 42, 18, 3, 123, 35, 181, 132, 212, 190, 193, 208, 117, 251, 195, 28, 48, 156, 2, 17, 0, 0, 0, 4, 31, 10, 83, 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