← previous blocknext block →recent activity
Analyzing
Block #85,183,775
19 transactions · 18 stateful · 2026-07-02 20:26:26 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,183,775 · 19 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
6w08w09w110w211w312w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74fd0a9b…3aaa
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x51a914cf…a822
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0xcdd7f0a5…d417
0x34b655…2a6f
8 touches
6 conflicts
0x7b7a78ce…a432
0x34b655…2a6f
6 touches
3 conflicts
0x1bab1ffb…2201
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x74fd0a9bd1…ea3aaa
Audit this contract →
← previous block·next block →recent activity