Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db1a57d6f34d6da64f76d1e75b19bf4ee55cc13db64ca246bf219adda0c535a3

Tx prefix hash: 24126336d856b681bcbb1a7560579dd2c4efeb8a16a2a3e3ce6bd445fd32c53b
Tx public key: 1bf7e0d6fbb1f79344473be08c667ef3a395b730a186fe89a5cbe5a32868605e
Timestamp: 1579292327 Timestamp [UCT]: 2020-01-17 20:18:47 Age [y:d:h:m:s]: 05:098:12:53:07
Block: 47841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220499 RingCT/type: yes/0
Extra: 011bf7e0d6fbb1f79344473be08c667ef3a395b730a186fe89a5cbe5a32868605e0211000000058a2ee0d9000000000000000000

1 output(s) for total of 426.072734444000 dcy

stealth address amount amount idx
00: 289d4bac57ea82f80a0fede621b716f9222f6147575a1383389674d2cc4913fd 426.072734444000 88376 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": 47851, "vin": [ { "gen": { "height": 47841 } } ], "vout": [ { "amount": 426072734444, "target": { "key": "289d4bac57ea82f80a0fede621b716f9222f6147575a1383389674d2cc4913fd" } } ], "extra": [ 1, 27, 247, 224, 214, 251, 177, 247, 147, 68, 71, 59, 224, 140, 102, 126, 243, 163, 149, 183, 48, 161, 134, 254, 137, 165, 203, 229, 163, 40, 104, 96, 94, 2, 17, 0, 0, 0, 5, 138, 46, 224, 217, 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