Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e20918151322598488831d222c754b66417378979c7d2256148c3158e89e53d

Tx prefix hash: d76b6c4b6cedf5c35aaf040ab193d1612c809893e1d36f26e032e54592df3a80
Tx public key: 7ceb8b0bad31578cc956c66a200f15e4015edd0b5518b8a876ac9c015db40d1c
Timestamp: 1639383316 Timestamp [UCT]: 2021-12-13 08:15:16 Age [y:d:h:m:s]: 03:023:17:10:37
Block: 394489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 795919 RingCT/type: yes/0
Extra: 017ceb8b0bad31578cc956c66a200f15e4015edd0b5518b8a876ac9c015db40d1c02110000000175e655a0000000000000000000

1 output(s) for total of 30.261785063000 dcy

stealth address amount amount idx
00: cab621025f5c878bb37a0b96a2521df11efbe9234655a1566fcf4d1377a4cdef 30.261785063000 792100 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": 394499, "vin": [ { "gen": { "height": 394489 } } ], "vout": [ { "amount": 30261785063, "target": { "key": "cab621025f5c878bb37a0b96a2521df11efbe9234655a1566fcf4d1377a4cdef" } } ], "extra": [ 1, 124, 235, 139, 11, 173, 49, 87, 140, 201, 86, 198, 106, 32, 15, 21, 228, 1, 94, 221, 11, 85, 24, 184, 168, 118, 172, 156, 1, 93, 180, 13, 28, 2, 17, 0, 0, 0, 1, 117, 230, 85, 160, 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