← previous blocknext block →recent activity
Analyzing
Block #83,621,767
33 transactions · 29 stateful · 2026-06-25 14:51:21 UTC
Parallelism
58/100
Blocked
66%
Avg conflicts / tx
2.88
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,621,767 · 33 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w27w39w010w111w212w313w414w515w616w717w818w919w1020w1121w1222w1328w129w132w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
26 touches
78 conflicts
0x4ed3af20…d87d
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 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
78 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity