← previous blocknext block →recent activity
Analyzing
Block #88,091,134
20 transactions · 19 stateful · 2026-07-16 08:05:28 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,091,134 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w110w011w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89678d1b…463e
0xa6afd3…d132
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9cea6ca2…570e
0x34b655…2a6f
4 touches
1 conflict
0xa523c16d…15cd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x89678d1b59…5a463e
Audit this contract →
← previous block·next block →recent activity