← previous blocknext block →recent activity
Analyzing
Block #87,281,793
20 transactions · 19 stateful · 2026-07-12 13:51:39 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,281,793 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w010w111w212w313w415w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0xdd194965…22d0
0x0a2fbf…29b1
10 touches
10 conflicts
0xdd194965…22d1
0x0a2fbf…29b1
10 touches
10 conflicts
0xdd194965…22d4
0x0a2fbf…29b1
10 touches
10 conflicts
0xef2802a8…1828
0x0a2fbf…29b1
10 touches
10 conflicts
0xef2802a8…1829
0x0a2fbf…29b1
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
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: 0x0a2fbf2d…f729b1
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity