← previous blocknext block →recent activity
Analyzing
Block #96,264,994
7 transactions · 5 stateful · 2026-08-15 17:37:38 UTC
Parallelism
43/100
Blocked
60%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,264,994 · 7 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x62738158…e746
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x6b17f7a0…af41
0x34b655…2a6f
4 touches
1 conflict
0x841c22c4…10c6
0x34b655…2a6f
4 touches
1 conflict
0x268e15db…68e8
0x34b655…2a6f
2 touches
0 conflicts
0x2ebbdd9c…4e7d
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
6 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity