← previous blocknext block →recent activity
Analyzing
Block #84,500,961
20 transactions · 18 stateful · 2026-06-29 16:32:06 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,500,961 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w18w19w210w311w412w014w116w017w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e45419…f17b
0x34b655…2a6f
8 touches
6 conflicts
0x8e739938…e7ab
0x34b655…2a6f
6 touches
3 conflicts
0x2754e960…bcc1
0x34b655…2a6f
6 touches
3 conflicts
0x3dec32b2…b3ad
0x34b655…2a6f
4 touches
1 conflict
0x3e2d319a…bd82
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8a7af3fd…72a6
0x34b655…2a6f
4 touches
1 conflict
0x8a7af3fd…72a7
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
6 conflicts on slot 0xe2e454194e…59f17b
Audit this contract →
← previous block·next block →recent activity