Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79825a4cecf0e86148e83655025a33f01562e77a433f263c5f8cde5860d8e60b

Tx prefix hash: 13a46a4590c16e83528c08e7de31807dce99160ea334014e6342abf9d9ca8b10
Tx public key: 4602607b366dd595aba70516bf1abfbb49528e2da7707e8e7c9e0dbbd1e2e47e
Timestamp: 1576927143 Timestamp [UCT]: 2019-12-21 11:19:03 Age [y:d:h:m:s]: 05:008:02:52:11
Block: 28903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155439 RingCT/type: yes/0
Extra: 014602607b366dd595aba70516bf1abfbb49528e2da7707e8e7c9e0dbbd1e2e47e021100000004ad433a0b000000000000000000

1 output(s) for total of 492.303843828000 dcy

stealth address amount amount idx
00: eb3e95d7bb4e21d385fc194afbb876803122338eb6a595c61bc85b7e53910241 492.303843828000 47719 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": 28913, "vin": [ { "gen": { "height": 28903 } } ], "vout": [ { "amount": 492303843828, "target": { "key": "eb3e95d7bb4e21d385fc194afbb876803122338eb6a595c61bc85b7e53910241" } } ], "extra": [ 1, 70, 2, 96, 123, 54, 109, 213, 149, 171, 167, 5, 22, 191, 26, 191, 187, 73, 82, 142, 45, 167, 112, 126, 142, 124, 158, 13, 187, 209, 226, 228, 126, 2, 17, 0, 0, 0, 4, 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