← previous blocknext block →recent activity
Analyzing
Block #86,959,770
13 transactions · 12 stateful · 2026-07-11 01:58:48 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,959,770 · 13 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
2w03w15w07w18w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3791570…f07a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x94de4d05…ad01
0x34b655…2a6f
8 touches
6 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
6 touches
3 conflicts
0x17a181c5…7236
0x34b655…2a6f
4 touches
1 conflict
0x2efd1517…0726
0x34b655…2a6f
4 touches
1 conflict
0x4fa2386a…7e33
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 0xa3791570c9…e9f07a
Audit this contract →
← previous block·next block →recent activity