← previous blocknext block →recent activity
Analyzing
Block #84,576,658
26 transactions · 21 stateful · 2026-06-30 00:57:23 UTC
Parallelism
69/100
Blocked
48%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,576,658 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w212w313w114w418w319w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd99b3b64…1c95
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x742072b0…1af8
0x34b655…2a6f
8 touches
7 conflicts
0x4384dd01…4f99
0x34b655…2a6f
8 touches
6 conflicts
0xea2644f5…8c97
0x34b655…2a6f
7 touches
8 conflicts
0x40b5f387…a164
0x34b655…2a6f
7 touches
6 conflicts
0x97fe3267…5e87
0x34b655…2a6f
6 touches
5 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 0xd99b3b6441…7a1c95
Audit this contract →
← previous block·next block →recent activity