← previous blocknext block →recent activity
Analyzing
Block #85,796,991
13 transactions · 12 stateful · 2026-07-05 16:31:15 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,796,991 · 13 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
1w02w13w05w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcccbf308…c92f
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0x7fa4a0af…f80e
0x065c9d…c394
3 touches
1 conflict
0x0b89150e…feef
0x065c9d…c394
3 touches
1 conflict
0x9df812f9…a233
0x065c9d…c394
3 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 0xcccbf30879…10c92f
Audit this contract →
← previous block·next block →recent activity