← previous blocknext block →recent activity
Analyzing
Block #83,398,214
24 transactions · 19 stateful · 2026-06-24 13:59:18 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,398,214 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w07w18w210w111w314w115w116w217w318w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708619a6…d52a
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x3b8acfe4…a3d9
0x34b655…2a6f
6 touches
3 conflicts
0x6f5fedd4…83f1
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x92793b0e…b68e
0x34b655…2a6f
6 touches
3 conflicts
0x9c7571b3…9605
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
6 conflicts on slot 0x708619a655…90d52a
Audit this contract →
← previous block·next block →recent activity