← previous blocknext block →recent activity
Analyzing
Block #85,982,953
24 transactions · 19 stateful · 2026-07-06 13:10:37 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,982,953 · 24 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
1w03w04w15w06w19w011w112w217w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff6a6ba1…10c1
0x34b655…2a6f
4 touches
1 conflict
0xb81b85ac…6126
0x34b655…2a6f
4 touches
1 conflict
0xbf140d9d…4923
0x34b655…2a6f
4 touches
1 conflict
0xc978dec7…e3d6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
1 conflict on slot 0xff6a6ba138…6310c1
Audit this contract →
← previous block·next block →recent activity