← previous blocknext block →recent activity
Analyzing
Block #83,411,215
25 transactions · 22 stateful · 2026-06-24 15:26:12 UTC
Parallelism
76/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,411,215 · 25 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
1w02w13w05w06w17w28w310w114w015w121w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2004b5f1…ff98
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x4efb974a…6126
0x34b655…2a6f
6 touches
3 conflicts
0x5d2b5661…df66
0x34b655…2a6f
6 touches
3 conflicts
0x70e66973…5d1b
0x34b655…2a6f
6 touches
3 conflicts
0x880707e5…4c68
0x34b655…2a6f
6 touches
3 conflicts
0xb9b4eff6…c3ef
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 0x2004b5f102…a7ff98
Audit this contract →
← previous block·next block →recent activity