← previous blocknext block →recent activity
Analyzing
Block #95,112,173
38 transactions · 35 stateful · 2026-08-11 16:44:03 UTC
Parallelism
92/100
Blocked
11%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,112,173 · 38 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w09w110w232w136w037w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4818eb90…13ea
0x34b655…2a6f
6 touches
3 conflicts
0x579ab5a4…4745
0x34b655…2a6f
6 touches
3 conflicts
0x1e10796e…6213
0x34b655…2a6f
4 touches
1 conflict
0x1e10796e…6214
0x34b655…2a6f
4 touches
1 conflict
0x27b96981…ef48
0x34b655…2a6f
4 touches
1 conflict
0x408cf8d2…f4f5
0x34b655…2a6f
4 touches
1 conflict
0x3de775b2…319b
0xa6afd3…d132
4 touches
1 conflict
0x0a2131b3…455e
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
3 conflicts on slot 0x4818eb9057…d113ea
Audit this contract →
← previous block·next block →recent activity