Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aa988827c19733149a2ee1d641de1569725411822ae2077ad9c7c3b74960a93

Tx prefix hash: 1cef4796b4e9d95ae9e078a3a1d5533e3749ec9a48325e7912daf33d4509894c
Tx public key: 27b078a3f018717d0913cf18a68fc84d9923219f860ea519c9541436d3d7d130
Timestamp: 1700833037 Timestamp [UCT]: 2023-11-24 13:37:17 Age [y:d:h:m:s]: 01:068:21:04:51
Block: 898653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310367 RingCT/type: yes/0
Extra: 0127b078a3f018717d0913cf18a68fc84d9923219f860ea519c9541436d3d7d13002110000000433af99f4000000000000000000

1 output(s) for total of 0.646233619000 dcy

stealth address amount amount idx
00: ecd30c4dec50d886e50319852572f1b73ba3c9ff90d33e3e2dc49c7f24f8be08 0.646233619000 1355080 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": 898663, "vin": [ { "gen": { "height": 898653 } } ], "vout": [ { "amount": 646233619, "target": { "key": "ecd30c4dec50d886e50319852572f1b73ba3c9ff90d33e3e2dc49c7f24f8be08" } } ], "extra": [ 1, 39, 176, 120, 163, 240, 24, 113, 125, 9, 19, 207, 24, 166, 143, 200, 77, 153, 35, 33, 159, 134, 14, 165, 25, 201, 84, 20, 54, 211, 215, 209, 48, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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