Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8946e971634a61f88933123cda2c8f5c1e44941f83a7a38c6d11c6c33a9ee9b8

Tx prefix hash: 40e7ec7cb5f00e2479c56ae4c65435524a0757e07f774952add3ffae0825547d
Tx public key: 8c883d224a2ee9fea052c29cfe54b648d08a44fea4edf3d944cda36e2a9f9f33
Timestamp: 1720139577 Timestamp [UCT]: 2024-07-05 00:32:57 Age [y:d:h:m:s]: 00:277:07:36:34
Block: 1058704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198145 RingCT/type: yes/0
Extra: 018c883d224a2ee9fea052c29cfe54b648d08a44fea4edf3d944cda36e2a9f9f330211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a76155d80423d3165b53530ff3bd3378cd70e7bad884616404f6375dee7f02 0.600000000000 1529161 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": 1058714, "vin": [ { "gen": { "height": 1058704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a76155d80423d3165b53530ff3bd3378cd70e7bad884616404f6375dee7f02" } } ], "extra": [ 1, 140, 136, 61, 34, 74, 46, 233, 254, 160, 82, 194, 156, 254, 84, 182, 72, 208, 138, 68, 254, 164, 237, 243, 217, 68, 205, 163, 110, 42, 159, 159, 51, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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