← previous blocknext block →recent activity
Analyzing
Block #87,714,987
13 transactions · 11 stateful · 2026-07-14 14:09:26 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,714,987 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7eb90864…574d
0x34b655…2a6f
6 touches
3 conflicts
0x7561f24a…4522
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0xb06a48e8…d6d1
0x34b655…2a6f
4 touches
1 conflict
0xb94312c7…10e3
0x34b655…2a6f
4 touches
1 conflict
0xbf78ee7f…e7fd
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x49edb376…e0b0
0xd32edf…ff58
3 touches
1 conflict
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
3 conflicts on slot 0x7eb9086438…db574d
Audit this contract →
← previous block·next block →recent activity