← previous blocknext block →recent activity
Analyzing
Block #87,592,636
23 transactions · 21 stateful · 2026-07-14 00:31:14 UTC
Parallelism
57/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,592,636 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w08w19w110w211w312w414w015w519w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0x469e824a…d814
0x34b655…2a6f
6 touches
3 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
6 touches
3 conflicts
0x4b628349…f327
0x34b655…2a6f
6 touches
3 conflicts
0x70040326…40e5
0x34b655…2a6f
6 touches
3 conflicts
0xc5490a87…0df8
0x34b655…2a6f
6 touches
3 conflicts
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