Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae042e8e3b3800b882481bd2d8cdf8917ef48155a26ba74ada6ce03b1c211278

Tx prefix hash: 02334ac06b93234a83244f6c5dbd808c23dfb65c9161faf7ea5df2f4f0010107
Tx public key: 14cc2d799175522d59c05d1e0bc684c534e89659658246aa265a25a5f984d977
Timestamp: 1704758616 Timestamp [UCT]: 2024-01-09 00:03:36 Age [y:d:h:m:s]: 01:082:13:46:42
Block: 931178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320121 RingCT/type: yes/0
Extra: 0114cc2d799175522d59c05d1e0bc684c534e89659658246aa265a25a5f984d97702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2e2899d8cee493df751d809a7ccf3ce0cf976467b596a71cce2c9e57521fc91 0.600000000000 1389072 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": 931188, "vin": [ { "gen": { "height": 931178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2e2899d8cee493df751d809a7ccf3ce0cf976467b596a71cce2c9e57521fc91" } } ], "extra": [ 1, 20, 204, 45, 121, 145, 117, 82, 45, 89, 192, 93, 30, 11, 198, 132, 197, 52, 232, 150, 89, 101, 130, 70, 170, 38, 90, 37, 165, 249, 132, 217, 119, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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