← previous blocknext block →recent activity
Analyzing
Block #83,623,207
19 transactions · 18 stateful · 2026-06-25 15:00:59 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,623,207 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w416w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fbabe09…8dd6
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0xf3f090c2…971e
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x708619a6…d52a
0x34b655…2a6f
8 touches
6 conflicts
0x3b8acfe4…a3d9
0x34b655…2a6f
7 touches
7 conflicts
0xffc2f21e…b393
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
10 conflicts on slot 0x9fbabe097e…9a8dd6
Audit this contract →
← previous block·next block →recent activity