Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab14b8053053a9c536d2a935e0296904d9c126b57172ff46ff674544fd578764

Tx prefix hash: 96d33c373cff8b85099aed948296a2a5637156b151d1e40530714d8428d887ea
Tx public key: ccb1b55f617744de3218d8b3fed0faade7dc505eab6cef554a540514cdf85c31
Timestamp: 1576643499 Timestamp [UCT]: 2019-12-18 04:31:39 Age [y:d:h:m:s]: 05:064:00:03:55
Block: 28251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193422 RingCT/type: yes/0
Extra: 01ccb1b55f617744de3218d8b3fed0faade7dc505eab6cef554a540514cdf85c3102110000003bad433a0b000000000000000000

1 output(s) for total of 494.758853313000 dcy

stealth address amount amount idx
00: ae78019111be7f8f0f9acb4e183c0bb71c8692e2627ceb2a9deced0813a5dba1 494.758853313000 46781 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": 28261, "vin": [ { "gen": { "height": 28251 } } ], "vout": [ { "amount": 494758853313, "target": { "key": "ae78019111be7f8f0f9acb4e183c0bb71c8692e2627ceb2a9deced0813a5dba1" } } ], "extra": [ 1, 204, 177, 181, 95, 97, 119, 68, 222, 50, 24, 216, 179, 254, 208, 250, 173, 231, 220, 80, 94, 171, 108, 239, 85, 74, 84, 5, 20, 205, 248, 92, 49, 2, 17, 0, 0, 0, 59, 173, 67, 58, 11, 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