Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2b493c93291770e2bfbafab7582eaa0903e795cfe6d3674b390c6ad81383fdd

Tx prefix hash: 1cd9657eee415df499db1d40c9a82f1f881c671927b9209e8ce3123404bf930f
Tx public key: 1a0811cf3927e60f4772d0d4e77789fef2d3a2e50ef43b28bf85383f0bd38fce
Timestamp: 1705472479 Timestamp [UCT]: 2024-01-17 06:21:19 Age [y:d:h:m:s]: 01:114:23:28:27
Block: 937084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343309 RingCT/type: yes/0
Extra: 011a0811cf3927e60f4772d0d4e77789fef2d3a2e50ef43b28bf85383f0bd38fce02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef43be30f7fd0b937ce256a1a210c56de5a4ae85b205b7114157e601b410bd16 0.600000000000 1395128 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": 937094, "vin": [ { "gen": { "height": 937084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef43be30f7fd0b937ce256a1a210c56de5a4ae85b205b7114157e601b410bd16" } } ], "extra": [ 1, 26, 8, 17, 207, 57, 39, 230, 15, 71, 114, 208, 212, 231, 119, 137, 254, 242, 211, 162, 229, 14, 244, 59, 40, 191, 133, 56, 63, 11, 211, 143, 206, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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