← previous blocknext block →recent activity
Analyzing
Block #86,239,639
26 transactions · 21 stateful · 2026-07-07 17:44:20 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,239,639 · 26 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
1w03w19w010w112w114w215w216w318w119w020w123w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x422d5490…52d9
0x34b655…2a6f
8 touches
6 conflicts
0x87b8f5fc…0dcc
0xd32edf…ff58
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd6479834…4e61
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
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 0x422d549061…1f52d9
Audit this contract →
← previous block·next block →recent activity