Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d76bbfc6ef707b4de5c24a709e39de0ca521696b244af8cb78cfe8303e343273

Tx prefix hash: 0e14ba9fa1e1f01699134ec182976543d0184c2fff33e5450d7fdd7f02e4d69f
Tx public key: 539d591c3d9a1beb82d1f0d4c1ea171f3eb80d531b05fe0f0ba1c2a2f104e573
Timestamp: 1706364218 Timestamp [UCT]: 2024-01-27 14:03:38 Age [y:d:h:m:s]: 01:000:19:05:35
Block: 944483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261653 RingCT/type: yes/0
Extra: 01539d591c3d9a1beb82d1f0d4c1ea171f3eb80d531b05fe0f0ba1c2a2f104e57302110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: add984123f5166699df89d2d350bda3dca3d20b8a637c2e871c1f2880fcefb8c 0.600000000000 1402733 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": 944493, "vin": [ { "gen": { "height": 944483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "add984123f5166699df89d2d350bda3dca3d20b8a637c2e871c1f2880fcefb8c" } } ], "extra": [ 1, 83, 157, 89, 28, 61, 154, 27, 235, 130, 209, 240, 212, 193, 234, 23, 31, 62, 184, 13, 83, 27, 5, 254, 15, 11, 161, 194, 162, 241, 4, 229, 115, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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