← previous blocknext block →recent activity
Analyzing
Block #84,526,846
30 transactions · 23 stateful · 2026-06-29 19:24:44 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.3
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,526,846 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w013w014w115w216w317w418w519w421w125w526w628w829w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x7c6d3d6d…9deb
0x34b655…2a6f
8 touches
6 conflicts
0x25de453d…9573
0x34b655…2a6f
6 touches
3 conflicts
0x2df5ccba…a51e
0x34b655…2a6f
6 touches
3 conflicts
0xac128389…db06
0x34b655…2a6f
6 touches
3 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity