← previous blocknext block →recent activity
Analyzing
Block #88,158,323
14 transactions · 10 stateful · 2026-07-16 15:35:09 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,158,323 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb36b8448…9a06
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
4 touches
1 conflict
0x1353affc…75e0
0x34b655…2a6f
4 touches
1 conflict
0x27b9caf2…c102
0x34b655…2a6f
4 touches
1 conflict
0x3733b87f…3410
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xb36b844891…269a06
Audit this contract →
← previous block·next block →recent activity