← previous blocknext block →recent activity
Analyzing
Block #84,617,758
17 transactions · 15 stateful · 2026-06-30 05:31:13 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,617,758 · 17 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
5w06w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x4384dd01…4f99
0x34b655…2a6f
8 touches
6 conflicts
0x98d3fc79…df78
0x34b655…2a6f
6 touches
3 conflicts
0xd0806a61…8350
0x34b655…2a6f
6 touches
3 conflicts
0xd89f212d…2bbf
0x34b655…2a6f
6 touches
3 conflicts
0xeb0f666f…02d5
0x34b655…2a6f
6 touches
3 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity