← previous blocknext block →recent activity
Analyzing
Block #86,791,290
19 transactions · 17 stateful · 2026-07-10 07:12:29 UTC
Parallelism
79/100
Blocked
24%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,791,290 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
5 touches
3 conflicts
0x42aad825…b067
0x34b655…2a6f
4 touches
1 conflict
0x44b0e9be…9ba8
0x34b655…2a6f
4 touches
1 conflict
0x44fc2746…0a53
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4cdf55e1…0f2d
0x34b655…2a6f
4 touches
1 conflict
0x66f7b1ee…a38b
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity