Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60d88e3ca4a9e0c041b9fa412b27776f3a5888eecc975af1cacca5556091795e

Tx prefix hash: f9341922e8703a9e89323e322d6245ac4cded058f7caaf695c02b487c46b7471
Tx public key: 8cbe90e40cb331e7d71e912a950896b07979a179217e0fbe40bb7436d96f9610
Timestamp: 1736871929 Timestamp [UCT]: 2025-01-14 16:25:29 Age [y:d:h:m:s]: 00:154:20:11:18
Block: 1197291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110368 RingCT/type: yes/0
Extra: 018cbe90e40cb331e7d71e912a950896b07979a179217e0fbe40bb7436d96f96100211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb8f04f84e43a10733511d125aa9adf79fdc22313e646015ec1e6157f52f75cb 0.600000000000 1683898 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": 1197301, "vin": [ { "gen": { "height": 1197291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb8f04f84e43a10733511d125aa9adf79fdc22313e646015ec1e6157f52f75cb" } } ], "extra": [ 1, 140, 190, 144, 228, 12, 179, 49, 231, 215, 30, 145, 42, 149, 8, 150, 176, 121, 121, 161, 121, 33, 126, 15, 190, 64, 187, 116, 54, 217, 111, 150, 16, 2, 17, 0, 0, 0, 6, 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