← previous blocknext block →recent activity
Analyzing
Block #84,460,531
44 transactions · 33 stateful · 2026-06-29 12:02:18 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.39
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #84,460,531 · 44 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
1w05w16w27w38w29w010w112w214w315w419w020w133w734w835w438w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x12dd43c9…22d9
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xd637b3…4160
10 touches
10 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0x0d593799…92f6
0x34b655…2a6f
10 touches
10 conflicts
0x016177de…bcb3
0xd32edf…ff58
9 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity