Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbefdd1e9a42534e0d8e470b1c0c103c09a8734b6f7e055df67d2b687a3ec217

Tx prefix hash: 5a3f5ec4a4702395ad2fbe6645fbdd774c25f3403159d2abfd6c62444ebba267
Tx public key: 94ab2756e576dc2fd94199567fcf48d014b51c547dc6fc0e9e4fd9e2e7f41ea0
Timestamp: 1708085006 Timestamp [UCT]: 2024-02-16 12:03:26 Age [y:d:h:m:s]: 00:272:15:05:51
Block: 958769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195190 RingCT/type: yes/0
Extra: 0194ab2756e576dc2fd94199567fcf48d014b51c547dc6fc0e9e4fd9e2e7f41ea002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3fd39a5ccb6940709e7798a5b44a454780afad771dbc778606ad715d736efd5 0.600000000000 1418130 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": 958779, "vin": [ { "gen": { "height": 958769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3fd39a5ccb6940709e7798a5b44a454780afad771dbc778606ad715d736efd5" } } ], "extra": [ 1, 148, 171, 39, 86, 229, 118, 220, 47, 217, 65, 153, 86, 127, 207, 72, 208, 20, 181, 28, 84, 125, 198, 252, 14, 158, 79, 217, 226, 231, 244, 30, 160, 2, 17, 0, 0, 0, 3, 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