← previous blocknext block →recent activity
Analyzing
Block #85,992,365
30 transactions · 25 stateful · 2026-07-06 14:13:34 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,992,365 · 30 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
2w03w14w25w010w112w113w014w217w121w222w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b077a8…e029
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xaa494bb9…6f98
0x34b655…2a6f
6 touches
3 conflicts
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
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 0xb9b077a82b…59e029
Audit this contract →
← previous block·next block →recent activity