← previous blocknext block →recent activity
Analyzing
Block #84,352,240
28 transactions · 23 stateful · 2026-06-29 00:00:32 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,352,240 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w112w015w122w123w224w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
6 touches
3 conflicts
0x454d8940…cfe7
0x34b655…2a6f
6 touches
3 conflicts
0x49b19c57…f607
0x34b655…2a6f
6 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x5ffc25fa…b119
0x34b655…2a6f
4 touches
1 conflict
0x68c8d31a…d33c
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity