← previous blocknext block →recent activity
Analyzing
Block #88,343,539
14 transactions · 13 stateful · 2026-07-17 12:14:15 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,343,539 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w29w310w411w513w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc477b5…1cf3
0x34b655…2a6f
6 touches
3 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x2a3bacb8…164b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x5cc477b5ef…3f1cf3
Audit this contract →
← previous block·next block →recent activity