Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cbdc3dfb5712f5b1f005fe3e2b6d440338a9318136971d246bbd49e19397aaf

Tx prefix hash: f0ff29af96ef4e97f5ed619b07829a889852c492c62e6e42d18ee6c4de298e7c
Tx public key: 09f0ce18d0d5ed8ce286fd2580adf9856edbaaf5a530f4e58949c4cfcd3962f3
Timestamp: 1726596057 Timestamp [UCT]: 2024-09-17 18:00:57 Age [y:d:h:m:s]: 00:114:10:01:46
Block: 1112233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81823 RingCT/type: yes/0
Extra: 0109f0ce18d0d5ed8ce286fd2580adf9856edbaaf5a530f4e58949c4cfcd3962f302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 115585d336e9492cd7aa8063ebd5731bead6ce496535635d59abecf257cb398c 0.600000000000 1591484 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": 1112243, "vin": [ { "gen": { "height": 1112233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "115585d336e9492cd7aa8063ebd5731bead6ce496535635d59abecf257cb398c" } } ], "extra": [ 1, 9, 240, 206, 24, 208, 213, 237, 140, 226, 134, 253, 37, 128, 173, 249, 133, 110, 219, 170, 245, 165, 48, 244, 229, 137, 73, 196, 207, 205, 57, 98, 243, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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