← previous blocknext block →recent activity
Analyzing
Block #83,633,875
31 transactions · 26 stateful · 2026-06-25 16:12:15 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.97
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,633,875 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w110w011w112w213w314w415w516w618w729w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xe2e45419…f17b
0x34b655…2a6f
8 touches
6 conflicts
0x286711a5…b3bf
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x2b2dce58…2f1d
0x34b655…2a6f
6 touches
3 conflicts
0x8773cb2e…9568
0x34b655…2a6f
6 touches
3 conflicts
0x8d3f06db…98cb
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity