← previous blocknext block →recent activity
Analyzing
Block #87,751,137
14 transactions · 11 stateful · 2026-07-14 18:11:23 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,751,137 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ed58b36…c5e5
0x34b655…2a6f
4 touches
1 conflict
0x6f46250b…3bf2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x808129fc…f97d
0x34b655…2a6f
4 touches
1 conflict
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x27279e7f…b1e6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0x5ed58b3680…35c5e5
Audit this contract →
← previous block·next block →recent activity