Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e30d3f12bb90736e5db5c4aaf97690cec50c96f8ffc43757660ff4da68c637f

Tx prefix hash: 9e9452cd6c51c1213894397d96b963ff89cca13a60f5e7d93cb0ebc009e1e335
Tx public key: 9d77afc791e849664087972addcd71a1ff57c6884d4bfc9adc6d3adc89a529d1
Timestamp: 1751297581 Timestamp [UCT]: 2025-06-30 15:33:01 Age [y:d:h:m:s]: 00:129:10:10:28
Block: 1315932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90670 RingCT/type: yes/0
Extra: 019d77afc791e849664087972addcd71a1ff57c6884d4bfc9adc6d3adc89a529d102110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc180d099641b35c0bfa2230ea4b1d2b03855ad94ff301c4fc175c51a1d6d20a 0.600000000000 1803589 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": 1315942, "vin": [ { "gen": { "height": 1315932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc180d099641b35c0bfa2230ea4b1d2b03855ad94ff301c4fc175c51a1d6d20a" } } ], "extra": [ 1, 157, 119, 175, 199, 145, 232, 73, 102, 64, 135, 151, 42, 221, 205, 113, 161, 255, 87, 198, 136, 77, 75, 252, 154, 220, 109, 58, 220, 137, 165, 41, 209, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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