← previous blocknext block →recent activity
Analyzing
Block #83,628,864
23 transactions · 21 stateful · 2026-06-25 15:38:46 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,628,864 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w09w110w211w312w420w121w222w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93641233…06f5
0x34b655…2a6f
11 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x5396d712…a139
0x34b655…2a6f
10 touches
10 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xffb1ee54…7c2c
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x9364123348…4106f5
Audit this contract →
← previous block·next block →recent activity