← previous blocknext block →recent activity
Analyzing
Block #84,352,211
23 transactions · 18 stateful · 2026-06-29 00:00:21 UTC
Parallelism
87/100
Blocked
39%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,352,211 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w07w110w011w112w213w014w015w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x75194ada…a1c5
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x8fcf2308…746e
0x34b655…2a6f
4 touches
1 conflict
0xbbe32bfe…94ca
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity