← previous blocknext block →recent activity
Analyzing
Block #86,271,730
23 transactions · 22 stateful · 2026-07-07 21:18:38 UTC
Parallelism
74/100
Blocked
27%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,271,730 · 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
4w011w115w016w117w219w320w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x2439c0d8…8489
0x34b655…2a6f
6 touches
3 conflicts
0xc85f42b6…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x55a03051…2930
0x34b655…2a6f
6 touches
3 conflicts
0x178db37f…debb
0x34b655…2a6f
4 touches
3 conflicts
0x37773728…f3a4
0x34b655…2a6f
4 touches
1 conflict
0x5c820dd1…ffa9
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity