← previous blocknext block →recent activity
Analyzing
Block #84,334,366
28 transactions · 21 stateful · 2026-06-28 22:01:22 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,334,366 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w010w111w216w017w019w220w121w325w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fcf2308…746e
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
6 touches
3 conflicts
0x0833f1ab…71e7
0x34b655…2a6f
4 touches
1 conflict
0x190ab6a6…5132
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7c6984da…21e5
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
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
3 conflicts on slot 0x8fcf2308ed…e1746e
Audit this contract →
← previous block·next block →recent activity