← previous blocknext block →recent activity
Analyzing
Block #84,511,961
43 transactions · 35 stateful · 2026-06-29 17:45:31 UTC
Parallelism
60/100
Blocked
69%
Avg conflicts / tx
1.79
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #84,511,961 · 43 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w18w211w012w113w214w318w019w120w221w322w423w524w625w726w831w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x2e72f452…bd7a
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
10 touches
10 conflicts
0x9af72ba2…f151
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xd637b3…4160
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