← previous blocknext block →recent activity
Analyzing
Block #83,411,084
21 transactions · 19 stateful · 2026-06-24 15:25:19 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,411,084 · 21 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
2w03w04w15w26w37w010w111w213w314w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef3a4217…dec8
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xb7ec7347…b85c
0x34b655…2a6f
8 touches
6 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
8 touches
6 conflicts
0xdf37a93d…879b
0x34b655…2a6f
8 touches
6 conflicts
0xe155a04c…f267
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x0dcee2ef…bc61
0x34b655…2a6f
8 touches
6 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 0xef3a421748…1adec8
Audit this contract →
← previous block·next block →recent activity