Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 488e0bb7c9488b113f0e0d91e959a62aeaf9477e8c074be485febf6fddac12fd

Tx prefix hash: 6d611713a8cc1df602a6973bd06615f62b0eeea5026db67092f7d5296be84f58
Tx public key: 8b9b915351326093ad5420ec7cca7476fa1330bef089358eb3b91b19a11a4405
Timestamp: 1734790073 Timestamp [UCT]: 2024-12-21 14:07:53 Age [y:d:h:m:s]: 00:321:02:48:37
Block: 1180079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226985 RingCT/type: yes/0
Extra: 018b9b915351326093ad5420ec7cca7476fa1330bef089358eb3b91b19a11a4405021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0e9a9a88ce1d2c7d467bec48da2d5739a402bcd3a2d0298e7fafd5539fbd1cb 0.600000000000 1666484 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": 1180089, "vin": [ { "gen": { "height": 1180079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0e9a9a88ce1d2c7d467bec48da2d5739a402bcd3a2d0298e7fafd5539fbd1cb" } } ], "extra": [ 1, 139, 155, 145, 83, 81, 50, 96, 147, 173, 84, 32, 236, 124, 202, 116, 118, 250, 19, 48, 190, 240, 137, 53, 142, 179, 185, 27, 25, 161, 26, 68, 5, 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