← previous blocknext block →recent activity
Analyzing
Block #83,576,922
27 transactions · 25 stateful · 2026-06-25 09:51:55 UTC
Parallelism
30/100
Blocked
72%
Avg conflicts / tx
5.48
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #83,576,922 · 27 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w814w917w1018w1119w1221w1422w1523w1624w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
26 touches
78 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x157dbfb2…4089
0x34b655…2a6f
18 touches
36 conflicts
0xe64e6363…e676
0x34b655…2a6f
18 touches
36 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x022f72c3…07b6
0xc8689a…ee79
18 touches
36 conflicts
0x9863393c…ce7b
0x34b655…2a6f
16 touches
28 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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity