Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09efdb7f29736c79083abd585993c5623a5c898b2eecfb5ad0eb01925e6fa149

Tx prefix hash: 6cdd2be537219b4d23276b9a370fee058649e2a3e1ab58a3fdaf62698ad4684d
Tx public key: 5a0a1062c80c07d2cbb7147ad7f346ca00496a3be217d27f5646fd84e1dd5d6d
Timestamp: 1729584047 Timestamp [UCT]: 2024-10-22 08:00:47 Age [y:d:h:m:s]: 00:033:06:02:25
Block: 1136977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23758 RingCT/type: yes/0
Extra: 015a0a1062c80c07d2cbb7147ad7f346ca00496a3be217d27f5646fd84e1dd5d6d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 537ddef1b79bbcc864a65f1493f4c783d98d88bc922bdbcf29122780a53533f2 0.600000000000 1620382 of 15

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": 1136987, "vin": [ { "gen": { "height": 1136977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "537ddef1b79bbcc864a65f1493f4c783d98d88bc922bdbcf29122780a53533f2" } } ], "extra": [ 1, 90, 10, 16, 98, 200, 12, 7, 210, 203, 183, 20, 122, 215, 243, 70, 202, 0, 73, 106, 59, 226, 23, 210, 127, 86, 70, 253, 132, 225, 221, 93, 109, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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