← previous blocknext block →recent activity
Analyzing
Block #96,488,532
12 transactions · 12 stateful · 2026-08-16 12:21:56 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,488,532 · 12 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
2w03w14w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c5238c6…f2dc
0x34b655…2a6f
6 touches
3 conflicts
0xe999cbf5…d18a
0x34b655…2a6f
4 touches
1 conflict
0x8e300ef3…ca4b
0x34b655…2a6f
4 touches
1 conflict
0x9a89094e…f5b2
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
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
3 conflicts on slot 0x5c5238c656…aaf2dc
Audit this contract →
← previous block·next block →recent activity