← previous blocknext block →recent activity
Analyzing
Block #87,340,858
17 transactions · 16 stateful · 2026-07-12 20:26:38 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,340,858 · 17 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
1w02w14w05w06w17w28w310w011w112w413w515w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x924bac95…3f39
0x34b655…2a6f
10 touches
10 conflicts
0x7ea6a117…f2f2
0x34b655…2a6f
10 touches
10 conflicts
0xd064a456…b881
0x34b655…2a6f
8 touches
6 conflicts
0x073234ac…40a4
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x8b46e9d1…e148
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
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 0x924bac955e…793f39
Audit this contract →
← previous block·next block →recent activity