← previous blocknext block →recent activity
Analyzing
Block #83,638,874
31 transactions · 27 stateful · 2026-06-25 16:45:39 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.45
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,638,874 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w18w09w010w113w114w015w216w317w418w519w624w627w128w730w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x049cca71…b102
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0xbb3504d4…b05f
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
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
21 conflicts on slot 0x049cca710d…16b102
Audit this contract →
← previous block·next block →recent activity