← previous blocknext block →recent activity
Analyzing
Block #87,304,309
16 transactions · 15 stateful · 2026-07-12 16:22:12 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,304,309 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w38w010w311w414w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x460a21c2…87f1
0x34b655…2a6f
10 touches
10 conflicts
0xd4726587…6289
0x34b655…2a6f
8 touches
6 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x9ad66bbf…929c
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
10 conflicts on slot 0x460a21c21a…f387f1
Audit this contract →
← previous block·next block →recent activity