← previous blocknext block →recent activity
Analyzing
Block #88,088,813
16 transactions · 13 stateful · 2026-07-16 07:49:56 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,088,813 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w29w313w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78255c70…2734
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x78255c70…2733
0x34b655…2a6f
6 touches
3 conflicts
0x5da07701…7ea7
0x34b655…2a6f
4 touches
1 conflict
0x5e17e5be…d212
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9e4304bd…4606
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 0x78255c70bd…2a2734
Audit this contract →
← previous block·next block →recent activity