← previous blocknext block →recent activity
Analyzing
Block #95,737,283
20 transactions · 18 stateful · 2026-08-13 21:22:52 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,737,283 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w19w110w211w312w015w316w417w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc85f42b6…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x0431e51f…6f91
0x34b655…2a6f
4 touches
1 conflict
0x2648406a…d91d
0x34b655…2a6f
4 touches
1 conflict
0x44614953…f05c
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x620b761c…270e
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 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity