Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49c2c0a055c75edf7683f12a1d9e449a0756299bf492c91fea38d84ce8507f94

Tx prefix hash: 0d2c6edaacd341874805dc6751aee6a638dcb23b1a461b1999e812d76593c098
Tx public key: 5b33e8c5ac2c14cd460a31de5aa38e72ed517ca53afe3de084b9879a8b85cdec
Timestamp: 1725238382 Timestamp [UCT]: 2024-09-02 00:53:02 Age [y:d:h:m:s]: 00:270:07:36:31
Block: 1100990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193084 RingCT/type: yes/0
Extra: 015b33e8c5ac2c14cd460a31de5aa38e72ed517ca53afe3de084b9879a8b85cdec021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6cef02ef5b20c07be70180161b94d49cf4e490808c1623c58f883f1a5aaf072 0.600000000000 1576971 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": 1101000, "vin": [ { "gen": { "height": 1100990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6cef02ef5b20c07be70180161b94d49cf4e490808c1623c58f883f1a5aaf072" } } ], "extra": [ 1, 91, 51, 232, 197, 172, 44, 20, 205, 70, 10, 49, 222, 90, 163, 142, 114, 237, 81, 124, 165, 58, 254, 61, 224, 132, 185, 135, 154, 139, 133, 205, 236, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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