Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b563f1b7e5643baa662b3ec4b12bb3423b35814a06dceb811fb0cd98eeaf56ad

Tx prefix hash: 0eb6e2ac1f90bdcfe71befdf99868ed36ce445273f9559b4d707dd23b5317514
Tx public key: 4567c9919e8ec074e56774ea4862d41d76f25a0c535ac9f5928852790807864f
Timestamp: 1626792374 Timestamp [UCT]: 2021-07-20 14:46:14 Age [y:d:h:m:s]: 03:131:05:51:18
Block: 297644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 865432 RingCT/type: yes/0
Extra: 014567c9919e8ec074e56774ea4862d41d76f25a0c535ac9f5928852790807864f0211000001d96367b7e9000000000000000000

1 output(s) for total of 63.355214268000 dcy

stealth address amount amount idx
00: e20dfe27b3982a2b32ecd423eed3f611e217792f2a5d2132eeec347f1e14de2f 63.355214268000 622960 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": 297654, "vin": [ { "gen": { "height": 297644 } } ], "vout": [ { "amount": 63355214268, "target": { "key": "e20dfe27b3982a2b32ecd423eed3f611e217792f2a5d2132eeec347f1e14de2f" } } ], "extra": [ 1, 69, 103, 201, 145, 158, 142, 192, 116, 229, 103, 116, 234, 72, 98, 212, 29, 118, 242, 90, 12, 83, 90, 201, 245, 146, 136, 82, 121, 8, 7, 134, 79, 2, 17, 0, 0, 1, 217, 99, 103, 183, 233, 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