← previous blocknext block →recent activity
Analyzing
Block #88,364,248
23 transactions · 17 stateful · 2026-07-17 14:33:26 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,364,248 · 23 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
2w03w18w09w113w214w316w417w521w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd71e14b…864c
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xb76f7c01…c3a5
0x34b655…2a6f
6 touches
3 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x282e00e6…172b
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 0xbd71e14b56…ae864c
Audit this contract →
← previous block·next block →recent activity