Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f8dc2f921c045fb3c32d679c3c33d9806da6f0954ed1d74c5312dffe97c5e97

Tx prefix hash: 29117c8a5b804c476d04ddd0f1a7c5883da02a1b12f9842cd837f7580bdebce6
Tx public key: eca2151a10b829da6d1371ff3bd7541ff8517420ac119fe1dbb710cef71f2c29
Timestamp: 1700398294 Timestamp [UCT]: 2023-11-19 12:51:34 Age [y:d:h:m:s]: 01:120:21:59:16
Block: 895046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347609 RingCT/type: yes/0
Extra: 01eca2151a10b829da6d1371ff3bd7541ff8517420ac119fe1dbb710cef71f2c29021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.664264497000 dcy

stealth address amount amount idx
00: 118d24d5054a4cf132bc3edbf075d01894f118112c5b3c69415b94635541b624 0.664264497000 1351267 of 0

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": 895056, "vin": [ { "gen": { "height": 895046 } } ], "vout": [ { "amount": 664264497, "target": { "key": "118d24d5054a4cf132bc3edbf075d01894f118112c5b3c69415b94635541b624" } } ], "extra": [ 1, 236, 162, 21, 26, 16, 184, 41, 218, 109, 19, 113, 255, 59, 215, 84, 31, 248, 81, 116, 32, 172, 17, 159, 225, 219, 183, 16, 206, 247, 31, 44, 41, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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