← previous blocknext block →recent activity
Analyzing
Block #82,341,008
48 transactions · 35 stateful · 2026-06-19 16:14:16 UTC
Parallelism
71/100
Blocked
60%
Avg conflicts / tx
1.79
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #82,341,008 · 48 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
1w03w14w05w16w07w112w013w114w216w017w118w219w320w425w227w531w441w942w1043w1145w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
12 touches
15 conflicts
0x957c875f…b3f9
0x34b655…2a6f
12 touches
15 conflicts
0x7ba3d4ba…d55a
0xc8689a…ee79
10 touches
10 conflicts
0x08913286…f0df
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity