Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3ece51ed4b8f59eba190c266c37bd8b7f937f83f81583dfe5ce30c6fc188cfb

Tx prefix hash: d225384c5b4805fe09cc66113bcb5f2a9cf1ae5b8fec59498d3a3a7db9c6cf97
Tx public key: 836c3ba3a754e7a388755a886f1b673d25cf2435821e9da4fbf841aca05f21fa
Timestamp: 1622939695 Timestamp [UCT]: 2021-06-06 00:34:55 Age [y:d:h:m:s]: 03:174:07:50:56
Block: 272912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 889086 RingCT/type: yes/0
Extra: 01836c3ba3a754e7a388755a886f1b673d25cf2435821e9da4fbf841aca05f21fa02110000001d23fdb90b000000000000000000

1 output(s) for total of 76.513370147000 dcy

stealth address amount amount idx
00: 03c9e13e80d8aec34c9d31603726eab75bdbf8b28893149dc17cf29c241a71f3 76.513370147000 572688 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": 272922, "vin": [ { "gen": { "height": 272912 } } ], "vout": [ { "amount": 76513370147, "target": { "key": "03c9e13e80d8aec34c9d31603726eab75bdbf8b28893149dc17cf29c241a71f3" } } ], "extra": [ 1, 131, 108, 59, 163, 167, 84, 231, 163, 136, 117, 90, 136, 111, 27, 103, 61, 37, 207, 36, 53, 130, 30, 157, 164, 251, 248, 65, 172, 160, 95, 33, 250, 2, 17, 0, 0, 0, 29, 35, 253, 185, 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