← previous blocknext block →recent activity
Analyzing
Block #87,596,153
21 transactions · 18 stateful · 2026-07-14 00:54:47 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,596,153 · 21 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
4w05w16w07w18w29w010w314w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x0b1ccf85…4ace
0x34b655…2a6f
4 touches
1 conflict
0x10ef891f…d725
0x34b655…2a6f
4 touches
1 conflict
0x10ef891f…d726
0x34b655…2a6f
4 touches
1 conflict
0x219dfcd6…652d
0x34b655…2a6f
4 touches
1 conflict
0x26050074…6967
0x34b655…2a6f
4 touches
1 conflict
0x2dfde2ed…8801
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity