← previous blocknext block →recent activity
Analyzing
Block #83,670,397
20 transactions · 18 stateful · 2026-06-25 20:15:55 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,670,397 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w410w114w215w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d7f309d…5145
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xa4d96d30…d00c
0x34b655…2a6f
8 touches
6 conflicts
0xb670a63e…ead8
0x34b655…2a6f
8 touches
6 conflicts
0x913ebf0e…d816
0x34b655…2a6f
7 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x329f2f7d…dcff
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 0x5d7f309de2…775145
Audit this contract →
← previous block·next block →recent activity