← previous blocknext block →recent activity
Analyzing
Block #87,440,824
22 transactions · 16 stateful · 2026-07-13 07:35:07 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,440,824 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w310w412w519w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x67d8b378…f2f8
0x34b655…2a6f
8 touches
6 conflicts
0x22c44de4…44de
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xe7aba1c7…1141
0x34b655…2a6f
6 touches
3 conflicts
0x20067ecb…0e41
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity