← previous blocknext block →recent activity
Analyzing
Block #83,454,614
21 transactions · 20 stateful · 2026-06-24 20:16:08 UTC
Parallelism
48/100
Blocked
60%
Avg conflicts / tx
1.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,454,614 · 21 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w38w49w510w611w717w118w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
12 touches
15 conflicts
0xdf37a93d…879b
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0xe0f1ea2a…a95d
0x34b655…2a6f
10 touches
10 conflicts
0x07a0dea2…ca8c
0x34b655…2a6f
8 touches
6 conflicts
0x65fd43be…4681
0x34b655…2a6f
6 touches
3 conflicts
0xb0735dd6…e3d6
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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity