← previous blocknext block →recent activity
Analyzing
Block #87,590,045
20 transactions · 14 stateful · 2026-07-14 00:13:54 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,590,045 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w18w211w312w413w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ce640b…884a
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x1172247d…0022
0x34b655…2a6f
6 touches
3 conflicts
0x5e51fa73…5cc9
0x34b655…2a6f
6 touches
3 conflicts
0x588c5b6a…60d2
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 0x69ce640b96…ed884a
Audit this contract →
← previous block·next block →recent activity