← previous blocknext block →recent activity
Analyzing
Block #84,352,187
43 transactions · 40 stateful · 2026-06-29 00:00:11 UTC
Parallelism
77/100
Blocked
65%
Avg conflicts / tx
1.98
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,352,187 · 43 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w27w38w39w434w541w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x454d8940…cfe7
0x34b655…2a6f
10 touches
10 conflicts
0x3f7ad3a0…de3b
0x34b655…2a6f
10 touches
10 conflicts
0x501bfcdc…9888
0xd32edf…ff58
9 touches
10 conflicts
0x3614b052…4e53
0x34b655…2a6f
8 touches
6 conflicts
0x753da1ce…6bbd
0x34b655…2a6f
8 touches
6 conflicts
0xcffc17bc…3544
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity