← previous blocknext block →recent activity
Analyzing
Block #88,351,532
20 transactions · 16 stateful · 2026-07-17 13:07:46 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,351,532 · 20 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
3w04w06w18w012w114w215w316w418w019w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabb1c6c2…b883
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x388b63a9…5008
0x34b655…2a6f
4 touches
1 conflict
0x38948e75…437a
0x34b655…2a6f
4 touches
1 conflict
0x3ddd83da…7fb5
0x34b655…2a6f
4 touches
1 conflict
0x47d77fe3…3415
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x709c2293…6c55
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 0xabb1c6c2ab…09b883
Audit this contract →
← previous block·next block →recent activity