← previous blocknext block →recent activity
Analyzing
Block #87,503,670
23 transactions · 20 stateful · 2026-07-13 14:35:26 UTC
Parallelism
52/100
Blocked
55%
Avg conflicts / tx
2.04
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,503,670 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w19w210w311w412w515w618w719w820w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x87f29f74…7c8b
0x34b655…2a6f
10 touches
10 conflicts
0x1d73754c…2e95
0x34b655…2a6f
8 touches
6 conflicts
0x3d4c0233…20a5
0x34b655…2a6f
8 touches
6 conflicts
0x0adf48a7…c84a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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
21 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity