← previous blocknext block →recent activity
Analyzing
Block #84,461,757
42 transactions · 38 stateful · 2026-06-29 12:10:31 UTC
Parallelism
60/100
Blocked
61%
Avg conflicts / tx
2.43
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #84,461,757 · 42 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
1w02w13w24w05w16w07w19w311w012w113w014w117w018w119w220w321w422w535w1036w1137w1240w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x9540632c…78a0
0x34b655…2a6f
12 touches
15 conflicts
0x77dc4958…659e
0x34b655…2a6f
10 touches
10 conflicts
0x93d680fb…ac21
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
8 touches
6 conflicts
0x754c4500…fe4b
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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity