Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd33c6ef754b52fbfeb95e3d8928e02213af61d7dcf6cbeb880b1602d16b7ab3

Tx prefix hash: ed899e6b917519aa8921b9fbb6838c985b89562c37cf006f35ea54f8b2333890
Tx public key: abd9872bd613310b5adc3ef772f1aa53ad8536c9cd07b4dff2d8c8361d65747d
Timestamp: 1707858515 Timestamp [UCT]: 2024-02-13 21:08:35 Age [y:d:h:m:s]: 01:070:08:02:39
Block: 956896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311319 RingCT/type: yes/0
Extra: 01abd9872bd613310b5adc3ef772f1aa53ad8536c9cd07b4dff2d8c8361d65747d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef9bb0fb3894e7f469942c6fb91fa15884a3b70a510c24c48170843a1c5ddbe8 0.600000000000 1416208 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": 956906, "vin": [ { "gen": { "height": 956896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef9bb0fb3894e7f469942c6fb91fa15884a3b70a510c24c48170843a1c5ddbe8" } } ], "extra": [ 1, 171, 217, 135, 43, 214, 19, 49, 11, 90, 220, 62, 247, 114, 241, 170, 83, 173, 133, 54, 201, 205, 7, 180, 223, 242, 216, 200, 54, 29, 101, 116, 125, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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