Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62912af8454553634dd6b97d4e483fd53d72f61e80275a0af8b358e80e47e13f

Tx prefix hash: f6d12ac3b754e2d6aea787ac7ae604143333db20a81895fd67b0d8a371afe5b8
Tx public key: 08a489994a1706490bb3307adf69eccbd40e80c5e6a0717b195073859ad09f9f
Timestamp: 1577043618 Timestamp [UCT]: 2019-12-22 19:40:18 Age [y:d:h:m:s]: 05:007:21:15:14
Block: 29723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155416 RingCT/type: yes/0
Extra: 0108a489994a1706490bb3307adf69eccbd40e80c5e6a0717b195073859ad09f9f02110000000b8a2ee0d9000000000000000000

1 output(s) for total of 489.233542383000 dcy

stealth address amount amount idx
00: e906a79978f8af7cdd21a88282ecab4b824d8905e397a1efc97089ae01bc0b1f 489.233542383000 48949 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": 29733, "vin": [ { "gen": { "height": 29723 } } ], "vout": [ { "amount": 489233542383, "target": { "key": "e906a79978f8af7cdd21a88282ecab4b824d8905e397a1efc97089ae01bc0b1f" } } ], "extra": [ 1, 8, 164, 137, 153, 74, 23, 6, 73, 11, 179, 48, 122, 223, 105, 236, 203, 212, 14, 128, 197, 230, 160, 113, 123, 25, 80, 115, 133, 154, 208, 159, 159, 2, 17, 0, 0, 0, 11, 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