← previous blocknext block →recent activity
Analyzing
Block #96,257,016
8 transactions · 7 stateful · 2026-08-15 16:57:31 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,257,016 · 8 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
4w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x49b28397…e3f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0eaa3f4e…2992
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000a
0x0ff112…757f
2 touches
0 conflicts
0x0e246445…9e0e
0x34b655…2a6f
2 touches
0 conflicts
0x15bea02e…b807
0x34b655…2a6f
2 touches
0 conflicts
0x182a2a24…e089
0x34b655…2a6f
2 touches
0 conflicts
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity