← previous blocknext block →recent activity
Analyzing
Block #86,625,456
25 transactions · 18 stateful · 2026-07-09 12:43:43 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,625,456 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w110w211w312w413w514w624w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x1941b441…5889
0x34b655…2a6f
12 touches
15 conflicts
0x31519d10…f76b
0x34b655…2a6f
10 touches
10 conflicts
0x3559c176…9fe1
0x34b655…2a6f
10 touches
10 conflicts
0x4ff21e31…8ed4
0x34b655…2a6f
10 touches
10 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
10 touches
10 conflicts
0x1cbd009b…629b
0x34b655…2a6f
10 touches
10 conflicts
0x895303cc…6f57
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity