← previous blocknext block →recent activity
Analyzing
Block #87,625,493
17 transactions · 17 stateful · 2026-07-14 04:10:57 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,625,493 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w07w28w110w312w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x364289f7…f98a
0x34b655…2a6f
4 touches
1 conflict
0x3ca9a061…1f41
0x34b655…2a6f
4 touches
1 conflict
0x3f0792d7…4742
0x34b655…2a6f
4 touches
1 conflict
0x62cc9214…441b
0x34b655…2a6f
4 touches
1 conflict
0x78cbb28a…27c3
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity