← previous blocknext block →recent activity
Analyzing
Block #87,591,637
24 transactions · 21 stateful · 2026-07-14 00:24:33 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,591,637 · 24 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
1w02w06w07w18w29w310w411w512w613w716w118w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x2d8a87f4…9991
0x34b655…2a6f
10 touches
10 conflicts
0x5e3a31d1…7a6e
0x34b655…2a6f
10 touches
10 conflicts
0xa24365bc…5064
0x34b655…2a6f
10 touches
10 conflicts
0xcd206b7a…abf6
0x34b655…2a6f
10 touches
10 conflicts
0x1de49243…4aa3
0x34b655…2a6f
10 touches
10 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity