← previous blocknext block →recent activity
Analyzing
Block #83,628,270
13 transactions · 12 stateful · 2026-06-25 15:34:48 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
1.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,628,270 · 13 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
1w02w13w24w35w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0x124be23b…2cca
0x34b655…2a6f
4 touches
2 conflicts
0x86a6ec3e…da0e
0x34b655…2a6f
4 touches
1 conflict
0xc2ab3ad1…a6bc
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity