← previous blocknext block →recent activity
Analyzing
Block #93,345,801
20 transactions · 18 stateful · 2026-08-05 12:22:20 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,345,801 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w211w312w313w115w316w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x808129fc…f97d
0x34b655…2a6f
6 touches
3 conflicts
0xa6389d47…9a28
0x34b655…2a6f
6 touches
3 conflicts
0x2c390858…b1ed
0x34b655…2a6f
6 touches
3 conflicts
0x8b76e9f2…54ee
0x34b655…2a6f
4 touches
1 conflict
0x9421a154…d296
0x34b655…2a6f
4 touches
1 conflict
0x96b52d30…6f0e
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity