← previous blocknext block →recent activity
Analyzing
Block #85,894,631
21 transactions · 16 stateful · 2026-07-06 03:21:35 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,894,631 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w011w212w317w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10a166bc…7aca
0x34b655…2a6f
6 touches
3 conflicts
0xd2c4cc9f…26af
0x065c9d…c394
5 touches
3 conflicts
0x55c44947…8887
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x2ce2d49e…d185
0x1b6862…e19c
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 0x10a166bc27…0a7aca
Audit this contract →
← previous block·next block →recent activity