← previous blocknext block →recent activity
Analyzing
Block #96,150,760
25 transactions · 24 stateful · 2026-08-15 08:03:05 UTC
Parallelism
60/100
Blocked
67%
Avg conflicts / tx
2.04
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,150,760 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w18w19w210w211w312w413w514w618w320w421w523w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0x3464bbc5…a323
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0e4000ee…afb9
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity