← previous blocknext block →recent activity
Analyzing
Block #83,638,663
21 transactions · 16 stateful · 2026-06-25 16:44:14 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,638,663 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w514w619w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee7978e9…2869
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0xe64e6363…e676
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 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 0xee7978e97a…ed2869
Audit this contract →
← previous block·next block →recent activity