← previous blocknext block →recent activity
Analyzing
Block #83,581,243
22 transactions · 22 stateful · 2026-06-25 10:20:41 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,581,243 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w09w110w211w312w413w315w516w220w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 conflicts
0x571cb36d…3b3d
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xe64e6363…e676
0x34b655…2a6f
10 touches
10 conflicts
0x157dbfb2…4089
0x34b655…2a6f
10 touches
10 conflicts
0x93e10ba3…803d
0x34b655…2a6f
8 touches
6 conflicts
0x7ccb0c7e…7d31
0x34b655…2a6f
6 touches
3 conflicts
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
15 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity