← previous blocknext block →recent activity
Analyzing
Block #83,398,547
18 transactions · 15 stateful · 2026-06-24 14:01:32 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,398,547 · 18 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
1w02w13w24w05w07w09w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6632320…a3ce
0x34b655…2a6f
8 touches
6 conflicts
0x3b8acfe4…a3d9
0x34b655…2a6f
8 touches
6 conflicts
0x124be23b…2cca
0x34b655…2a6f
6 touches
4 conflicts
0x13aceb70…cf9f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
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
6 conflicts on slot 0xb6632320a3…16a3ce
Audit this contract →
← previous block·next block →recent activity