← previous blocknext block →recent activity
Analyzing
Block #87,734,640
28 transactions · 24 stateful · 2026-07-14 16:21:00 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,734,640 · 28 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
3w04w15w06w08w110w211w317w019w220w321w123w324w325w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x5f251b96…6054
0x34b655…2a6f
6 touches
3 conflicts
0xe3f2706b…d3ec
0x34b655…2a6f
6 touches
3 conflicts
0x153d1e25…10ea
0x34b655…2a6f
4 touches
1 conflict
0x16ecedc8…53ea
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x3243881c…00ab
0x34b655…2a6f
4 touches
1 conflict
0x46e3da6b…72ca
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 0x94ba9c4a07…0c41d8
Audit this contract →
← previous block·next block →recent activity