← previous blocknext block →recent activity
Analyzing
Block #86,386,121
29 transactions · 24 stateful · 2026-07-08 10:02:48 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.34
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,386,121 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w216w018w319w420w022w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x380edffa…078e
0xd32edf…ff58
5 touches
3 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xbcc2ea3e…8ea3
0x34b655…2a6f
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
3 conflicts on slot 0x7aad02c682…feb979
Audit this contract →
← previous block·next block →recent activity