Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5efea2754a827375aa7b634fa6c16f5267ccb7cbead89969a3f2ad6f96db30c

Tx prefix hash: 3e303478ca5c4c95e6e702c102c7f8563badbaa3f4f94ec052ca4c1687b60e83
Tx public key: 8260b7a8bfc419e591955f5996f8a2b058e51f615de9c1699b7f03108bf352e9
Timestamp: 1578123520 Timestamp [UCT]: 2020-01-04 07:38:40 Age [y:d:h:m:s]: 05:002:19:40:25
Block: 38333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152133 RingCT/type: yes/0
Extra: 018260b7a8bfc419e591955f5996f8a2b058e51f615de9c1699b7f03108bf352e902110000000aff58ae94000000000000000000

1 output(s) for total of 458.136820243000 dcy

stealth address amount amount idx
00: c860abc428bb6d538df5940fa592826cb8dfd21eba4aeba0c7dbc49f3e6c6a20 458.136820243000 65309 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": 38343, "vin": [ { "gen": { "height": 38333 } } ], "vout": [ { "amount": 458136820243, "target": { "key": "c860abc428bb6d538df5940fa592826cb8dfd21eba4aeba0c7dbc49f3e6c6a20" } } ], "extra": [ 1, 130, 96, 183, 168, 191, 196, 25, 229, 145, 149, 95, 89, 150, 248, 162, 176, 88, 229, 31, 97, 93, 233, 193, 105, 155, 127, 3, 16, 139, 243, 82, 233, 2, 17, 0, 0, 0, 10, 255, 88, 174, 148, 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