← previous blocknext block →recent activity
Analyzing
Block #87,296,901
24 transactions · 19 stateful · 2026-07-12 15:32:42 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,296,901 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w18w29w010w111w212w313w416w217w318w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xbc94dfe1…0b3d
0x34b655…2a6f
6 touches
3 conflicts
0xdb564c7f…72f9
0x34b655…2a6f
6 touches
3 conflicts
0xdbd174e4…b6f8
0x34b655…2a6f
6 touches
3 conflicts
0x1aef6331…1390
0x34b655…2a6f
4 touches
1 conflict
0x1e48811e…2e39
0x34b655…2a6f
4 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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity