Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11aa94b8319b149129cd41783cbfe46b2ea8a2347fe1d5a344d047d27bd093f9

Tx prefix hash: 1c742c0a028b08613e6ca702673c6a3f7c22800d593a19ee80bc9697606cd4c2
Tx public key: 2d02f8630e90ff9faf27e908554b8b621c98966bf35fc06953d12d779ffc4a45
Timestamp: 1733679237 Timestamp [UCT]: 2024-12-08 17:33:57 Age [y:d:h:m:s]: 00:111:17:18:00
Block: 1170869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79622 RingCT/type: yes/0
Extra: 012d02f8630e90ff9faf27e908554b8b621c98966bf35fc06953d12d779ffc4a450211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d97f0e3da951e07e262ef4d368ea5285f4b5bc7680a2af3ce43fc612619e78bf 0.600000000000 1656604 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": 1170879, "vin": [ { "gen": { "height": 1170869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d97f0e3da951e07e262ef4d368ea5285f4b5bc7680a2af3ce43fc612619e78bf" } } ], "extra": [ 1, 45, 2, 248, 99, 14, 144, 255, 159, 175, 39, 233, 8, 85, 75, 139, 98, 28, 152, 150, 107, 243, 95, 192, 105, 83, 209, 45, 119, 159, 252, 74, 69, 2, 17, 0, 0, 0, 1, 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