← previous blocknext block →recent activity
Analyzing
Block #83,666,171
30 transactions · 24 stateful · 2026-06-25 19:47:43 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
1.43
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,666,171 · 30 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
1w02w05w19w010w111w113w214w315w416w517w618w719w820w923w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xf86f15cd…38af
0x34b655…2a6f
8 touches
6 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
8 touches
6 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9e7c6b67…7db2
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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity