Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca4cb74856407adcda8d98d423bbc952133509b9dd438cda8683314dea9db27f

Tx prefix hash: 99eaf681587c11b79106ff29a4952056ab5d87b162dca019d8fc364e04822781
Tx public key: 1117aae9d74061cb51932bab39bb0cfa5bf4dcad17b8ba684846ba2846f36c5d
Timestamp: 1698935081 Timestamp [UCT]: 2023-11-02 14:24:41 Age [y:d:h:m:s]: 01:218:18:03:16
Block: 883130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417378 RingCT/type: yes/0
Extra: 011117aae9d74061cb51932bab39bb0cfa5bf4dcad17b8ba684846ba2846f36c5d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.727484448000 dcy

stealth address amount amount idx
00: 4f17eabc2105e7d3481e86823d1ea7772df747124a997e966531aa30c4a144c8 0.727484448000 1338818 of 0

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": 883140, "vin": [ { "gen": { "height": 883130 } } ], "vout": [ { "amount": 727484448, "target": { "key": "4f17eabc2105e7d3481e86823d1ea7772df747124a997e966531aa30c4a144c8" } } ], "extra": [ 1, 17, 23, 170, 233, 215, 64, 97, 203, 81, 147, 43, 171, 57, 187, 12, 250, 91, 244, 220, 173, 23, 184, 186, 104, 72, 70, 186, 40, 70, 243, 108, 93, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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