← previous blocknext block →recent activity
Analyzing
Block #88,351,974
25 transactions · 23 stateful · 2026-07-17 13:10:43 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,351,974 · 25 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
2w06w07w18w29w010w211w312w316w017w118w219w422w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xbef49d3e…f9bb
0x34b655…2a6f
6 touches
3 conflicts
0xf565ea1f…4245
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x75854a6e…5d6e
0x34b655…2a6f
4 touches
1 conflict
0x963c13ae…147a
0x34b655…2a6f
4 touches
1 conflict
0xa99bc1cb…67c9
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
6 conflicts on slot 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity