← previous blocknext block →recent activity
Analyzing
Block #85,898,896
14 transactions · 11 stateful · 2026-07-06 03:50:01 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,898,896 · 14 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
1w03w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18d511d2…2a7c
0x065c9d…c394
4 touches
1 conflict
0x197f2061…1e56
0x065c9d…c394
3 touches
1 conflict
0x967dd09f…2983
0x065c9d…c394
3 touches
1 conflict
0x53f7a673…0ad9
0x065c9d…c394
2 touches
0 conflicts
0x919d5105…a3b0
0x065c9d…c394
2 touches
0 conflicts
0xe449691d…be5e
0x065c9d…c394
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 0xafd867b7ed…d92b2e
Audit this contract →
← previous block·next block →recent activity