← previous blocknext block →recent activity
Analyzing
Block #83,454,221
20 transactions · 16 stateful · 2026-06-24 20:13:30 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,454,221 · 20 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
4w06w17w28w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x049cca71…b102
0x34b655…2a6f
8 touches
6 conflicts
0x126a0344…4465
0x34b655…2a6f
8 touches
6 conflicts
0xfadc118d…5d64
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x393dfd73…ff57
0x34b655…2a6f
4 touches
1 conflict
0x39bcab17…f79f
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x049cca710d…16b102
Audit this contract →
← previous block·next block →recent activity