← previous blocknext block →recent activity
Analyzing
Block #84,522,007
30 transactions · 24 stateful · 2026-06-29 18:52:30 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
0.9
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #84,522,007 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w19w010w111w212w314w418w519w520w121w122w223w226w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c7763f6…89be
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x019ded9d…6fa0
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x87b97d35…627d
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 0x1c7763f6c9…dd89be
Audit this contract →
← previous block·next block →recent activity