← previous blocknext block →recent activity
Analyzing
Block #84,620,095
20 transactions · 17 stateful · 2026-06-30 05:46:42 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,620,095 · 20 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
1w03w04w15w09w010w111w212w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea2644f5…8c97
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8822b247…dd44
0x34b655…2a6f
6 touches
3 conflicts
0x9966da31…0d0f
0x34b655…2a6f
6 touches
3 conflicts
0xd2274a53…9d6a
0x34b655…2a6f
6 touches
3 conflicts
0x24227bc5…cb16
0x34b655…2a6f
4 touches
1 conflict
0x27d815d2…5ca9
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 0xea2644f55c…128c97
Audit this contract →
← previous block·next block →recent activity