← previous blocknext block →recent activity
Analyzing
Block #85,969,624
22 transactions · 15 stateful · 2026-07-06 11:41:34 UTC
Parallelism
91/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,969,624 · 22 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w111w014w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc34a9068…6b7f
0x34b655…2a6f
4 touches
1 conflict
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0xde03d008…98a5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb3366bba…2a1a
0xd32edf…ff58
3 touches
1 conflict
0x9b335b21…0093
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
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 0xc34a90682b…146b7f
Audit this contract →
← previous block·next block →recent activity