← previous blocknext block →recent activity
Analyzing
Block #83,853,373
27 transactions · 23 stateful · 2026-06-26 16:36:52 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,853,373 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w19w010w011w112w216w017w318w420w221w324w126w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9540632c…78a0
0x34b655…2a6f
8 touches
6 conflicts
0x103e429e…066b
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x8726ff39…3be8
0x34b655…2a6f
4 touches
1 conflict
0x876e6153…323b
0x34b655…2a6f
4 touches
1 conflict
0x9dbefc67…4855
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x9540632c24…9778a0
Audit this contract →
← previous block·next block →recent activity