← previous blocknext block →recent activity
Analyzing
Block #83,411,091
35 transactions · 33 stateful · 2026-06-24 15:25:22 UTC
Parallelism
66/100
Blocked
64%
Avg conflicts / tx
2.26
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #83,411,091 · 35 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w37w38w010w111w012w113w214w315w416w517w618w719w420w522w129w830w932w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2004b5f1…ff98
0x34b655…2a6f
18 touches
36 conflicts
0xef3a4217…dec8
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xc40c2185…51ae
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x5d2b5661…df66
0x34b655…2a6f
12 touches
15 conflicts
0x7c8e50e4…c598
0x34b655…2a6f
12 touches
15 conflicts
0xa0173442…ce88
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0x2004b5f102…a7ff98
Audit this contract →
← previous block·next block →recent activity