← previous blocknext block →recent activity
Analyzing
Block #86,126,855
24 transactions · 19 stateful · 2026-07-07 05:11:20 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,126,855 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w214w018w319w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x55a03051…2930
0x34b655…2a6f
4 touches
1 conflict
0x5c683f40…ae1f
0x34b655…2a6f
4 touches
1 conflict
0x6c34b38f…c9e0
0x34b655…2a6f
4 touches
1 conflict
0xa8dbe7b0…8bad
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity