← previous blocknext block →recent activity
Analyzing
Block #84,996,652
22 transactions · 20 stateful · 2026-07-01 23:36:01 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,996,652 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w28w19w010w011w113w214w118w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xda84f122…80e5
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x424eca3b…f2ab
0xa6afd3…d132
4 touches
1 conflict
0xdc120748…ff36
0xa6afd3…d132
4 touches
1 conflict
0xeb2adc73…6152
0xa6afd3…d132
4 touches
1 conflict
0x6bdb9869…7558
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
3 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity