Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e501ec9b3f7fa36c31a09642dc10ebbb3c2e06950d19b94a00cf704a0b1524

Tx prefix hash: 462fc2cf87fff074a9196e8cfb0be89dbebcd5a49faafb73c9afa5a4ef5707ab
Tx public key: b298723f78121e92dee9be1efdb992d4b9c1e5bc3a08630172ca8e5e460b1a36
Timestamp: 1643565978 Timestamp [UCT]: 2022-01-30 18:06:18 Age [y:d:h:m:s]: 03:009:08:09:58
Block: 428648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 785836 RingCT/type: yes/0
Extra: 01b298723f78121e92dee9be1efdb992d4b9c1e5bc3a08630172ca8e5e460b1a36021100000002cb8520c2000000000000000000

1 output(s) for total of 23.319087166000 dcy

stealth address amount amount idx
00: 286bdf6e6a92e5efed495bddc2378fba3120440eb2b06e225a951f300f8f9cfc 23.319087166000 838094 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": 428658, "vin": [ { "gen": { "height": 428648 } } ], "vout": [ { "amount": 23319087166, "target": { "key": "286bdf6e6a92e5efed495bddc2378fba3120440eb2b06e225a951f300f8f9cfc" } } ], "extra": [ 1, 178, 152, 114, 63, 120, 18, 30, 146, 222, 233, 190, 30, 253, 185, 146, 212, 185, 193, 229, 188, 58, 8, 99, 1, 114, 202, 142, 94, 70, 11, 26, 54, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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