← previous blocknext block →recent activity
Analyzing
Block #87,732,028
31 transactions · 30 stateful · 2026-07-14 16:03:33 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,732,028 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w18w310w011w012w113w214w315w419w020w122w124w225w229w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x0122c555…4443
0xd32edf…ff58
7 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x0ea75628…bd71
0x34b655…2a6f
6 touches
3 conflicts
0x3726966a…669d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity