Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24649626990da014d3044de82d32cb453ff49c971995742742c7efbb5142db43

Tx prefix hash: 26a1a58e936d9bb9eacc70607109316711e57400aff7bdd3d29ec8cb443470d6
Tx public key: 5855d6581f654f6078c817b5410d4c7d86d82b8cbe8b85e9fece0fad72ab586e
Timestamp: 1580885781 Timestamp [UCT]: 2020-02-05 06:56:21 Age [y:d:h:m:s]: 04:326:02:01:14
Block: 58836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124644 RingCT/type: yes/0
Extra: 015855d6581f654f6078c817b5410d4c7d86d82b8cbe8b85e9fece0fad72ab586e02110000000249b77a3d000000000000000000

1 output(s) for total of 391.789441699000 dcy

stealth address amount amount idx
00: cbe3aef61663b6c0bdf688f4e76771e2304dd1fa17f672f93de93485a563398f 391.789441699000 108748 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": 58846, "vin": [ { "gen": { "height": 58836 } } ], "vout": [ { "amount": 391789441699, "target": { "key": "cbe3aef61663b6c0bdf688f4e76771e2304dd1fa17f672f93de93485a563398f" } } ], "extra": [ 1, 88, 85, 214, 88, 31, 101, 79, 96, 120, 200, 23, 181, 65, 13, 76, 125, 134, 216, 43, 140, 190, 139, 133, 233, 254, 206, 15, 173, 114, 171, 88, 110, 2, 17, 0, 0, 0, 2, 73, 183, 122, 61, 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