← previous blocknext block →recent activity
Analyzing
Block #83,665,266
24 transactions · 19 stateful · 2026-06-25 19:41:38 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,665,266 · 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
3w04w17w28w011w012w113w214w316w017w119w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06571461…d6f0
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x6b47245e…a342
0x34b655…2a6f
8 touches
6 conflicts
0x85b992ec…db0e
0x34b655…2a6f
8 touches
6 conflicts
0xe64e6363…e676
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xfd4e2262…cd8c
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 0x065714618c…2dd6f0
Audit this contract →
← previous block·next block →recent activity