Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 544b8ab6523aa918e91025e384a23c92f709bddb85ab3cf9fc0f154c93522618

Tx prefix hash: 7e81c411b1daca2ca55aded3deb6c07a9200f6b2b26601f60df224fd2e681bc6
Tx public key: 3aad9e8bcdfd102c28d6b1c176ffca345639a0034303b7b047594d64091a1a27
Timestamp: 1577689942 Timestamp [UCT]: 2019-12-30 07:12:22 Age [y:d:h:m:s]: 05:065:16:01:22
Block: 34840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196720 RingCT/type: yes/0
Extra: 013aad9e8bcdfd102c28d6b1c176ffca345639a0034303b7b047594d64091a1a27021100000003d81c26c0000000000000000000

1 output(s) for total of 470.501998445000 dcy

stealth address amount amount idx
00: 3eb85c50c156bf99d04252a3be97f086e56f296fc13c78c749996ef0e3ce98f9 470.501998445000 58699 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": 34850, "vin": [ { "gen": { "height": 34840 } } ], "vout": [ { "amount": 470501998445, "target": { "key": "3eb85c50c156bf99d04252a3be97f086e56f296fc13c78c749996ef0e3ce98f9" } } ], "extra": [ 1, 58, 173, 158, 139, 205, 253, 16, 44, 40, 214, 177, 193, 118, 255, 202, 52, 86, 57, 160, 3, 67, 3, 183, 176, 71, 89, 77, 100, 9, 26, 26, 39, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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