← previous blocknext block →recent activity
Analyzing
Block #83,398,161
22 transactions · 17 stateful · 2026-06-24 13:58:57 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,398,161 · 22 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
1w02w15w06w17w28w39w410w512w614w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x9c7571b3…9605
0x34b655…2a6f
10 touches
10 conflicts
0xa1571d54…ae41
0x34b655…2a6f
10 touches
10 conflicts
0xc2ab3ad1…a6bc
0x34b655…2a6f
10 touches
10 conflicts
0xbcba4059…bec4
0x34b655…2a6f
6 touches
3 conflicts
0x3b8acfe4…a3d9
0x34b655…2a6f
4 touches
1 conflict
0x5200f5f6…b7be
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity