Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69c01ba9433c1a3818605bb4bc4f82db4419cabe06d5da427b9e0f5e8dcf371f

Tx prefix hash: a92043727c921267e5e0ef5b3abc7b9c04c87cc1b71835658f1ffa2dac962260
Tx public key: 374d7445c02c84920ef07229c32a3b523a96ace4fcc1a7c4d4efdd62bc24c583
Timestamp: 1729787530 Timestamp [UCT]: 2024-10-24 16:32:10 Age [y:d:h:m:s]: 00:152:09:23:35
Block: 1138657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108706 RingCT/type: yes/0
Extra: 01374d7445c02c84920ef07229c32a3b523a96ace4fcc1a7c4d4efdd62bc24c5830211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffcca6ff6f5bda90fd792e5e34cbc4ae2c17096f65de13f83845bcdb8b906673 0.600000000000 1622354 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": 1138667, "vin": [ { "gen": { "height": 1138657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffcca6ff6f5bda90fd792e5e34cbc4ae2c17096f65de13f83845bcdb8b906673" } } ], "extra": [ 1, 55, 77, 116, 69, 192, 44, 132, 146, 14, 240, 114, 41, 195, 42, 59, 82, 58, 150, 172, 228, 252, 193, 167, 196, 212, 239, 221, 98, 188, 36, 197, 131, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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