← previous blocknext block →recent activity
Analyzing
Block #88,077,342
14 transactions · 13 stateful · 2026-07-16 06:33:14 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,077,342 · 14 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
1w02w16w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x320701d5…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x57e95ab1…d5ef
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0xad15ca0d…a3d5
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x959dc95c…6d84
0x34b655…2a6f
3 touches
1 conflict
0xd8fd2add…50fc
0x2b46c0…1669
2 touches
0 conflicts
0x00000000…003d
0x851145…3f07
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 0x320701d57e…e5f9f3
Audit this contract →
← previous block·next block →recent activity