← previous blocknext block →recent activity
Analyzing
Block #96,035,993
8 transactions · 6 stateful · 2026-08-14 22:25:48 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,035,993 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x931bd7a5…b6b9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xed270adc…e8ac
0x34b655…2a6f
4 touches
1 conflict
0x0f2d79dd…d939
0x34b655…2a6f
2 touches
0 conflicts
0x15f864cd…d17b
0x34b655…2a6f
2 touches
0 conflicts
0x1e947b24…b988
0x34b655…2a6f
2 touches
0 conflicts
0x236533a6…52ac
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
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
1 conflict on slot 0x931bd7a585…f2b6b9
Audit this contract →
← previous block·next block →recent activity