Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ef6e9b6a5bd874b5a94745dd49afd77fe1154348bfb1ce17c998d61575693c1

Tx prefix hash: 79988ee902b10d2ae0704a6c06ba5977a3c259bb5d3fd55dca911f2a31996128
Tx public key: 71a831433bdc94175f48539eeefd1ecf1bc0f0e186abc4a91bba0c9b85970347
Timestamp: 1702320429 Timestamp [UCT]: 2023-12-11 18:47:09 Age [y:d:h:m:s]: 01:142:12:43:24
Block: 910988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363018 RingCT/type: yes/0
Extra: 0171a831433bdc94175f48539eeefd1ecf1bc0f0e186abc4a91bba0c9b8597034702110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8736868b8bf7ae5f3a797b7a24361cddb6277151cdc31648de9f6f06a68e13d2 0.600000000000 1368163 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": 910998, "vin": [ { "gen": { "height": 910988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8736868b8bf7ae5f3a797b7a24361cddb6277151cdc31648de9f6f06a68e13d2" } } ], "extra": [ 1, 113, 168, 49, 67, 59, 220, 148, 23, 95, 72, 83, 158, 238, 253, 30, 207, 27, 192, 240, 225, 134, 171, 196, 169, 27, 186, 12, 155, 133, 151, 3, 71, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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