← previous blocknext block →recent activity
Analyzing
Block #84,498,301
23 transactions · 19 stateful · 2026-06-29 16:14:21 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,498,301 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w29w010w111w212w313w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8e739938…e7ab
0x34b655…2a6f
8 touches
6 conflicts
0x2754e960…bcc1
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x00e21a9f…3583
0x34b655…2a6f
6 touches
3 conflicts
0x04f26bce…2a8e
0x34b655…2a6f
6 touches
3 conflicts
0x69568050…da32
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity