← previous blocknext block →recent activity
Analyzing
Block #88,092,665
19 transactions · 17 stateful · 2026-07-16 08:15:43 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,092,665 · 19 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
1w02w15w06w07w18w211w312w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x220a8541…6431
0x34b655…2a6f
4 touches
1 conflict
0x3180a80d…ab00
0x34b655…2a6f
4 touches
1 conflict
0x3807752c…c23b
0x34b655…2a6f
4 touches
1 conflict
0x66309899…07b3
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity