← previous blocknext block →recent activity
Analyzing
Block #84,120,440
77 transactions · 62 stateful · 2026-06-27 22:16:34 UTC
Parallelism
78/100
Blocked
77%
Avg conflicts / tx
4.03
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #84,120,440 · 77 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w315w419w120w221w322w423w524w625w726w827w928w1029w1130w1231w1333w1435w1560w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
34 touches
136 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
32 touches
120 conflicts
0x00000000…003d
0xa6afd3…d132
30 touches
105 conflicts
0x3287e4ec…eaa3
0xa6afd3…d132
30 touches
105 conflicts
0x19ce481d…6c36
0x34b655…2a6f
28 touches
91 conflicts
0x75cdffd8…c217
0x34b655…2a6f
28 touches
91 conflicts
0x40970e69…da50
0x69df8a…6292
28 touches
91 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
28 touches
91 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
136 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity