← previous blocknext block →recent activity
Analyzing
Block #88,092,396
30 transactions · 24 stateful · 2026-07-16 08:13:55 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,092,396 · 30 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
3w04w19w010w112w013w115w216w320w422w525w227w228w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xb44d5376…33cc
0x34b655…2a6f
6 touches
3 conflicts
0x55012d1a…3907
0x2b46c0…1669
4 touches
1 conflict
0xb5c4826d…bdd6
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x1dd79365…4bab
0x34b655…2a6f
4 touches
1 conflict
0x5f16286b…7e43
0x34b655…2a6f
4 touches
1 conflict
0x64e5f38d…187c
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity