← previous blocknext block →recent activity
Analyzing
Block #86,683,744
25 transactions · 23 stateful · 2026-07-09 19:14:20 UTC
Parallelism
64/100
Blocked
61%
Avg conflicts / tx
1.96
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,683,744 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w511w612w717w822w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x727fbce7…0c80
0x34b655…2a6f
18 touches
36 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
18 touches
36 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
16 touches
28 conflicts
0x63c900f4…2600
0x34b655…2a6f
16 touches
28 conflicts
0xa1571d54…ae41
0x34b655…2a6f
16 touches
28 conflicts
0xc1aad6e5…9135
0x34b655…2a6f
16 touches
28 conflicts
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity