← previous blocknext block →recent activity
Analyzing
Block #88,087,619
14 transactions · 13 stateful · 2026-07-16 07:41:58 UTC
Parallelism
50/100
Blocked
62%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,087,619 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w48w59w612w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd147ef4d…36ef
0x34b655…2a6f
8 touches
6 conflicts
0x574a8378…b246
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x1ec7ada6…505b
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x4c214bb3…c5d3
0x34b655…2a6f
4 touches
1 conflict
0x64e5f38d…187c
0x34b655…2a6f
4 touches
1 conflict
0x671e007b…1761
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 0xd147ef4dea…d636ef
Audit this contract →
← previous block·next block →recent activity