← previous blocknext block →recent activity
Analyzing
Block #84,487,964
35 transactions · 25 stateful · 2026-06-29 15:05:21 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
1.23
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #84,487,964 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w110w211w318w019w120w221w322w423w524w625w728w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xa6464996…3af9
0x34b655…2a6f
10 touches
10 conflicts
0xc458b1a7…eed4
0x34b655…2a6f
10 touches
10 conflicts
0x206f4379…e08a
0x34b655…2a6f
10 touches
10 conflicts
0xdf9957df…8d42
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x616ec3dd…5ce1
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity