← previous blocknext block →recent activity
Analyzing
Block #83,631,831
45 transactions · 42 stateful · 2026-06-25 15:58:35 UTC
Parallelism
62/100
Blocked
69%
Avg conflicts / tx
3.24
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,631,831 · 45 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w28w49w010w112w213w314w015w116w217w318w419w520w621w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0x022f72c3…07b6
0xc8689a…ee79
22 touches
55 conflicts
0x5396d712…a139
0x34b655…2a6f
22 touches
55 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
22 touches
55 conflicts
0xe334a6b5…173c
0x34b655…2a6f
20 touches
45 conflicts
0xffc2f21e…b393
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xaa7ee7…f0e4
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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity