← previous blocknext block →recent activity
Analyzing
Block #86,947,648
15 transactions · 14 stateful · 2026-07-11 00:37:48 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,947,648 · 15 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
5w06w18w29w310w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7545436b…012e
0x34b655…2a6f
8 touches
6 conflicts
0x836c7065…ae3f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2170bea4…4723
0x34b655…2a6f
6 touches
3 conflicts
0xe684760e…ece0
0x34b655…2a6f
6 touches
3 conflicts
0x2170bea4…4722
0x34b655…2a6f
6 touches
3 conflicts
0x2efd1517…0726
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 0x7545436ba6…f5012e
Audit this contract →
← previous block·next block →recent activity