Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ddf05af78a524cecdacbee3dbee3708bdf1594429db76f2b98d0a7e448b644

Tx prefix hash: cceb02ef80749c3fd75f003bf21b0f0c8a9aa6394cf835e8e1382588ff8d8243
Tx public key: 5c7263e21cdfa868f6408c0487478e94d9b8c1da3f8bf2dec74e00d6c771ffb3
Timestamp: 1682282990 Timestamp [UCT]: 2023-04-23 20:49:50 Age [y:d:h:m:s]: 02:005:03:26:18
Block: 745114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525822 RingCT/type: yes/0
Extra: 015c7263e21cdfa868f6408c0487478e94d9b8c1da3f8bf2dec74e00d6c771ffb3021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.085106378000 dcy

stealth address amount amount idx
00: 796e070f8fcf94ccb6ab902d1470bc3d0f79f5eb1920e6f847dd135dbeb39b34 2.085106378000 1192533 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": 745124, "vin": [ { "gen": { "height": 745114 } } ], "vout": [ { "amount": 2085106378, "target": { "key": "796e070f8fcf94ccb6ab902d1470bc3d0f79f5eb1920e6f847dd135dbeb39b34" } } ], "extra": [ 1, 92, 114, 99, 226, 28, 223, 168, 104, 246, 64, 140, 4, 135, 71, 142, 148, 217, 184, 193, 218, 63, 139, 242, 222, 199, 78, 0, 214, 199, 113, 255, 179, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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