← previous blocknext block →recent activity
Analyzing
Block #84,460,797
20 transactions · 17 stateful · 2026-06-29 12:04:05 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,460,797 · 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
1w02w03w15w26w19w010w011w112w213w314w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e45419…f17b
0x34b655…2a6f
10 touches
10 conflicts
0x826cce18…251c
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x35de07e6…7751
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x3437f15c…790b
0x34b655…2a6f
6 touches
3 conflicts
0xdb067026…9eb8
0x69df8a…6292
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
10 conflicts on slot 0xe2e454194e…59f17b
Audit this contract →
← previous block·next block →recent activity