← previous blocknext block →recent activity
Analyzing
Block #87,711,178
23 transactions · 23 stateful · 2026-07-14 13:43:55 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,711,178 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w18w09w115w016w117w218w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a8af3c2…e4ae
0x34b655…2a6f
6 touches
3 conflicts
0x39cbc853…9a82
0x34b655…2a6f
6 touches
3 conflicts
0x324ec4d3…f156
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x6e088aaa…3972
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x70f537e8…399b
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
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
3 conflicts on slot 0x9a8af3c2bb…d8e4ae
Audit this contract →
← previous block·next block →recent activity