Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25ef736cc3ba2326a681649b8e4adcde7d7979fa4f38eb532aca3d3619bb763e

Tx prefix hash: 622b842008d4473119e0a0857a0a69dc10ddc2f6807786f8ceeaaae6f3f382e6
Tx public key: 871df3c03dd1f423bb0683193184b23046a92f660d45c59a7099e1bae7004b85
Timestamp: 1699293208 Timestamp [UCT]: 2023-11-06 17:53:28 Age [y:d:h:m:s]: 01:094:19:03:50
Block: 885889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328913 RingCT/type: yes/0
Extra: 01871df3c03dd1f423bb0683193184b23046a92f660d45c59a7099e1bae7004b850211000000074b8f5122000000000000000000

1 output(s) for total of 0.712331250000 dcy

stealth address amount amount idx
00: eb08973dea10b89c2f36cb784f764299959973b9629716a64828eb2c93897b6e 0.712331250000 1341682 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": 885899, "vin": [ { "gen": { "height": 885889 } } ], "vout": [ { "amount": 712331250, "target": { "key": "eb08973dea10b89c2f36cb784f764299959973b9629716a64828eb2c93897b6e" } } ], "extra": [ 1, 135, 29, 243, 192, 61, 209, 244, 35, 187, 6, 131, 25, 49, 132, 178, 48, 70, 169, 47, 102, 13, 69, 197, 154, 112, 153, 225, 186, 231, 0, 75, 133, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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