← previous blocknext block →recent activity
Analyzing
Block #88,157,097
36 transactions · 25 stateful · 2026-07-16 15:26:56 UTC
Parallelism
89/100
Blocked
44%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,157,097 · 36 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
1w02w010w111w212w313w014w119w021w124w025w026w127w228w233w134w135w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d989c17…e984
0x34b655…2a6f
6 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x00000000…0000
0x354d92…66fb
4 touches
1 conflict
0x00000000…0001
0x354d92…66fb
4 touches
1 conflict
0x38b5b2ce…c5bb
0x354d92…66fb
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 0x8d989c177f…b7e984
Audit this contract →
← previous block·next block →recent activity