Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f39c3bd91638a450ef7bbae74e562456c7532967fc2a57a1904dba208a0a9caa

Tx prefix hash: f9b32d0ea56ad180f251ce21df29b4d907db6b204d2f9a46664b79946b904dd2
Tx public key: 565c67a5619940aa0c21650610c0649ea06ee00e98d3ee28718749db9b7bead5
Timestamp: 1704507264 Timestamp [UCT]: 2024-01-06 02:14:24 Age [y:d:h:m:s]: 01:140:06:10:21
Block: 929083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361411 RingCT/type: yes/0
Extra: 01565c67a5619940aa0c21650610c0649ea06ee00e98d3ee28718749db9b7bead502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad6a2f79dc87af9e7bc081e3dc7e627d5441ab1fc42ee6518b5077884d2ea03e 0.600000000000 1386951 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": 929093, "vin": [ { "gen": { "height": 929083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad6a2f79dc87af9e7bc081e3dc7e627d5441ab1fc42ee6518b5077884d2ea03e" } } ], "extra": [ 1, 86, 92, 103, 165, 97, 153, 64, 170, 12, 33, 101, 6, 16, 192, 100, 158, 160, 110, 224, 14, 152, 211, 238, 40, 113, 135, 73, 219, 155, 123, 234, 213, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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