← previous blocknext block →recent activity
Analyzing
Block #87,626,438
18 transactions · 17 stateful · 2026-07-14 04:17:16 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,626,438 · 18 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
3w04w15w26w37w48w513w617w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x9d9b4da9…ecf3
0x34b655…2a6f
12 touches
15 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
12 touches
15 conflicts
0x49f75237…44f4
0x34b655…2a6f
10 touches
10 conflicts
0x1de49243…4aa3
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0xa83ace75…e803
0x34b655…2a6f
10 touches
10 conflicts
0xa24365bc…5064
0x34b655…2a6f
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity