← previous blocknext block →recent activity
Analyzing
Block #83,622,581
60 transactions · 50 stateful · 2026-06-25 14:56:47 UTC
Parallelism
67/100
Blocked
76%
Avg conflicts / tx
4.98
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,622,581 · 60 txs across 20 waves · depth 20
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
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w011w112w213w314w415w516w617w718w819w920w1021w1122w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
40 touches
190 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
26 touches
78 conflicts
0x7c6984da…21e5
0x34b655…2a6f
18 touches
36 conflicts
0xab981df1…2941
0x34b655…2a6f
16 touches
28 conflicts
0xc2dcae88…f07a
0x34b655…2a6f
16 touches
28 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
16 touches
28 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
12 touches
15 conflicts
0xdb067026…9eb8
0x69df8a…6292
12 touches
15 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
190 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity