Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7d7b2039360783a5c7b6e53c54212867115790ae820eeeb3abde0c2207e080f

Tx prefix hash: 80b0559a61d4e34e63b62e2c044e609cef093ffb8a2ae764802d03a3ea27fdea
Tx public key: 8106741f2e606f472000723b4bf26280f50a94ad1cdb4a6bc906015c7b358e36
Timestamp: 1578816608 Timestamp [UCT]: 2020-01-12 08:10:08 Age [y:d:h:m:s]: 05:294:01:18:10
Block: 43751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1358094 RingCT/type: yes/0
Extra: 018106741f2e606f472000723b4bf26280f50a94ad1cdb4a6bc906015c7b358e360211000000134ac5aa02000000000000000000

1 output(s) for total of 439.577664476000 dcy

stealth address amount amount idx
00: 3494cd95b2db987855d2cd34d9b0adbaaab934fe2006350aba6214cd4f35e6d9 439.577664476000 79362 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": 43761, "vin": [ { "gen": { "height": 43751 } } ], "vout": [ { "amount": 439577664476, "target": { "key": "3494cd95b2db987855d2cd34d9b0adbaaab934fe2006350aba6214cd4f35e6d9" } } ], "extra": [ 1, 129, 6, 116, 31, 46, 96, 111, 71, 32, 0, 114, 59, 75, 242, 98, 128, 245, 10, 148, 173, 28, 219, 74, 107, 201, 6, 1, 92, 123, 53, 142, 54, 2, 17, 0, 0, 0, 19, 74, 197, 170, 2, 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