Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7056eccd14ec621f1195c4dcf5d13730b40426793ce39f94ec699646a67052fc

Tx prefix hash: ae28b9b293d5c5745f2bad842887c63f3ea6d76a9069f4cda4dce693080bf4ce
Tx public key: b52aa05a0f42429a1c62e9dcb9408d5792f3c516845036d7fd67f356331a5e36
Timestamp: 1729036981 Timestamp [UCT]: 2024-10-16 00:03:01 Age [y:d:h:m:s]: 00:000:16:22:52
Block: 1132498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471 RingCT/type: yes/0
Extra: 01b52aa05a0f42429a1c62e9dcb9408d5792f3c516845036d7fd67f356331a5e360211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 226ae08ed094e19459d9943718657318a4c6bd7e79c5718700a22124a94207a2 0.600000000000 1615419 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": 1132508, "vin": [ { "gen": { "height": 1132498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "226ae08ed094e19459d9943718657318a4c6bd7e79c5718700a22124a94207a2" } } ], "extra": [ 1, 181, 42, 160, 90, 15, 66, 66, 154, 28, 98, 233, 220, 185, 64, 141, 87, 146, 243, 197, 22, 132, 80, 54, 215, 253, 103, 243, 86, 51, 26, 94, 54, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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