← previous blocknext block →recent activity
Analyzing
Block #83,410,075
28 transactions · 21 stateful · 2026-06-24 15:18:37 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,410,075 · 28 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
7w08w19w210w313w015w017w119w020w124w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6632320…a3ce
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3ed61588…0c31
0x34b655…2a6f
6 touches
3 conflicts
0x8e507257…71c1
0x34b655…2a6f
6 touches
3 conflicts
0x9c7571b3…9605
0x34b655…2a6f
6 touches
3 conflicts
0x9e4890bd…fd9d
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
10 conflicts on slot 0xb6632320a3…16a3ce
Audit this contract →
← previous block·next block →recent activity