← previous blocknext block →recent activity
Analyzing
Block #83,623,321
22 transactions · 16 stateful · 2026-06-25 15:01:44 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,623,321 · 22 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
5w06w17w28w39w419w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x4ed3af20…d87d
0x34b655…2a6f
6 touches
3 conflicts
0x23c5c9ed…69bb
0x34b655…2a6f
4 touches
1 conflict
0x2475df98…9661
0x34b655…2a6f
4 touches
1 conflict
0x3b8acfe4…a3d9
0x34b655…2a6f
4 touches
1 conflict
0x3db23932…9be6
0x34b655…2a6f
4 touches
1 conflict
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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