← previous blocknext block →recent activity
Analyzing
Block #88,343,366
18 transactions · 15 stateful · 2026-07-17 12:13:06 UTC
Parallelism
78/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,343,366 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x427d1120…4eb1
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x446c9ed6…c25c
0x34b655…2a6f
2 touches
0 conflicts
0x519e0fef…7303
0x34b655…2a6f
2 touches
0 conflicts
0x5bdae4ca…5d23
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity