← previous blocknext block →recent activity
Analyzing
Block #86,945,842
14 transactions · 13 stateful · 2026-07-11 00:25:46 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,945,842 · 14 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
6w07w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xecb52d36…abcf
0x34b655…2a6f
6 touches
3 conflicts
0x2efac4f6…3abf
0x34b655…2a6f
6 touches
3 conflicts
0x4b3b0587…0912
0x34b655…2a6f
6 touches
3 conflicts
0xecb52d36…abce
0x34b655…2a6f
6 touches
3 conflicts
0xab49be51…d6e3
0x34b655…2a6f
4 touches
1 conflict
0xc93fa87c…2bea
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity