← previous blocknext block →recent activity
Analyzing
Block #84,354,686
17 transactions · 17 stateful · 2026-06-29 00:16:52 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,354,686 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w010w111w313w414w515w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd6d4eb00…30f3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x36194a06…44d2
0x34b655…2a6f
4 touches
1 conflict
0x4a3a411f…1e74
0x34b655…2a6f
4 touches
1 conflict
0x646051ca…f19a
0x34b655…2a6f
4 touches
1 conflict
0x6c9541ce…9135
0x34b655…2a6f
4 touches
1 conflict
0x7425a853…a582
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity