← previous blocknext block →recent activity
Analyzing
Block #86,493,783
23 transactions · 20 stateful · 2026-07-08 22:02:18 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,493,783 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w210w015w016w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x74888025…a5b8
0x34b655…2a6f
8 touches
6 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
6 touches
3 conflicts
0xac951277…1862
0x34b655…2a6f
6 touches
3 conflicts
0x11431f9d…42c5
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x6f58168d…ea24
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 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity