Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9563978d4203d540888761d13d7c331c40677fe52ffe13880c6c5ca58c2ce1b2

Tx prefix hash: 1d0d4a56677de56ab06bc67d1523046cf6ea03dfbc1e57273a3e370573ef6a22
Tx public key: b1bcec5578bb2e3ba6567a34ee1a79c6a7c193b6adede64d9835bfe0ac56d0db
Timestamp: 1721724143 Timestamp [UCT]: 2024-07-23 08:42:23 Age [y:d:h:m:s]: 00:267:22:59:45
Block: 1071842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191432 RingCT/type: yes/0
Extra: 01b1bcec5578bb2e3ba6567a34ee1a79c6a7c193b6adede64d9835bfe0ac56d0db02110000002de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8be3d653e8a6c2713b9ea2023a6bee5a5a5634dbba75abf30a6360f345d2c848 0.600000000000 1544221 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": 1071852, "vin": [ { "gen": { "height": 1071842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8be3d653e8a6c2713b9ea2023a6bee5a5a5634dbba75abf30a6360f345d2c848" } } ], "extra": [ 1, 177, 188, 236, 85, 120, 187, 46, 59, 166, 86, 122, 52, 238, 26, 121, 198, 167, 193, 147, 182, 173, 237, 230, 77, 152, 53, 191, 224, 172, 86, 208, 219, 2, 17, 0, 0, 0, 45, 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