← previous blocknext block →recent activity
Analyzing
Block #87,643,830
20 transactions · 16 stateful · 2026-07-14 06:13:31 UTC
Parallelism
55/100
Blocked
56%
Avg conflicts / tx
1.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,643,830 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w49w511w618w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
14 touches
21 conflicts
0x42c7fd6d…fc6c
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x8b501dcf…1040
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x1716b13d…99cc
0xc8689a…ee79
8 touches
6 conflicts
0x313f4bc7…ebbb
0x34b655…2a6f
8 touches
6 conflicts
0x60806778…9ead
0x34b655…2a6f
8 touches
6 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 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity