Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d97e7e1027fbaa0b2d9851433cf8c75226539d4fbed9228884b8dcc75b20052

Tx prefix hash: 7cd442a0a4283086e30e560bf4d3746a49fdb9c5ec041cbcbe84d0a6524288f3
Tx public key: c88ba29d5e8cfd6fb99f89ce792282f689b7b3b63aa455a9555f723b640dfe8c
Timestamp: 1726141885 Timestamp [UCT]: 2024-09-12 11:51:25 Age [y:d:h:m:s]: 00:101:08:06:21
Block: 1108466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72507 RingCT/type: yes/0
Extra: 01c88ba29d5e8cfd6fb99f89ce792282f689b7b3b63aa455a9555f723b640dfe8c021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f036f4d390abdfd9513a134b341f3ee9bb9babcff4791979496202c03fac040 0.600000000000 1586375 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": 1108476, "vin": [ { "gen": { "height": 1108466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f036f4d390abdfd9513a134b341f3ee9bb9babcff4791979496202c03fac040" } } ], "extra": [ 1, 200, 139, 162, 157, 94, 140, 253, 111, 185, 159, 137, 206, 121, 34, 130, 246, 137, 183, 179, 182, 58, 164, 85, 169, 85, 95, 114, 59, 100, 13, 254, 140, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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