← previous blocknext block →recent activity
Analyzing
Block #83,655,078
18 transactions · 18 stateful · 2026-06-25 18:33:47 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,655,078 · 18 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
3w07w18w29w310w411w514w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6fd65c0…3a8a
0x34b655…2a6f
12 touches
15 conflicts
0xa80684c9…3948
0x34b655…2a6f
10 touches
10 conflicts
0x0722b113…100b
0x34b655…2a6f
10 touches
10 conflicts
0xc169c8e9…3e10
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xf714ce17…3c39
0x34b655…2a6f
8 touches
6 conflicts
0x46d5a052…ff2e
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
15 conflicts on slot 0xe6fd65c0f9…793a8a
Audit this contract →
← previous block·next block →recent activity