← previous blocknext block →recent activity
Analyzing
Block #83,758,405
23 transactions · 20 stateful · 2026-06-26 06:03:02 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,758,405 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w29w310w412w313w019w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
12 touches
15 conflicts
0x58c77739…7c7d
0x34b655…2a6f
8 touches
6 conflicts
0x31a4cbfd…23a9
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x76477ddf…b8f8
0xc8689a…ee79
6 touches
3 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0xd33e70b0…1515
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity