Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2abd9284051348996fdcfb6479f6eabfcc8109a44ecf9f8ff9d6c25514e86be9

Tx prefix hash: d74ccf4e7029c8c2512a8b61f2835f5491cfb0a57e1d81d3ccb8cd756a038cc8
Tx public key: 4088c571ef0a1d9968f50795e97c5cbf71d968fcd22097a39887d88add782473
Timestamp: 1726289441 Timestamp [UCT]: 2024-09-14 04:50:41 Age [y:d:h:m:s]: 00:222:14:21:57
Block: 1109692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158939 RingCT/type: yes/0
Extra: 014088c571ef0a1d9968f50795e97c5cbf71d968fcd22097a39887d88add782473021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca1a5d600f7f9e7a541d7b16650420506baa576001bcf042f8e6ac438f73a424 0.600000000000 1588039 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": 1109702, "vin": [ { "gen": { "height": 1109692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca1a5d600f7f9e7a541d7b16650420506baa576001bcf042f8e6ac438f73a424" } } ], "extra": [ 1, 64, 136, 197, 113, 239, 10, 29, 153, 104, 245, 7, 149, 233, 124, 92, 191, 113, 217, 104, 252, 210, 32, 151, 163, 152, 135, 216, 138, 221, 120, 36, 115, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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