← previous blocknext block →recent activity
Analyzing
Block #87,498,618
20 transactions · 18 stateful · 2026-07-13 14:01:38 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,498,618 · 20 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
3w05w06w19w110w211w312w014w415w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x092832cd…7b28
0x34b655…2a6f
6 touches
3 conflicts
0x0a51d6fa…1ea1
0x34b655…2a6f
4 touches
1 conflict
0x18ca6535…87c1
0x34b655…2a6f
4 touches
1 conflict
0x1bc07c63…d6ad
0x34b655…2a6f
4 touches
1 conflict
0x1d72f627…aa57
0x34b655…2a6f
4 touches
1 conflict
0x35075a55…56b4
0x34b655…2a6f
4 touches
1 conflict
0x469e824a…d814
0x34b655…2a6f
4 touches
1 conflict
0x5ce8e9ad…6207
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 0x092832cdd7…187b28
Audit this contract →
← previous block·next block →recent activity