← previous blocknext block →recent activity
Analyzing
Block #85,991,376
18 transactions · 15 stateful · 2026-07-06 14:06:58 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,991,376 · 18 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
1w07w18w09w112w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x64c57c87…5e42
0x34b655…2a6f
4 touches
1 conflict
0x2c506459…5351
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x36c2bbc0…753a
0x34b655…2a6f
3 touches
1 conflict
0x286d7a84…5f57
0xd32edf…ff58
3 touches
1 conflict
0x5ed593e1…1e59
0x065c9d…c394
3 touches
1 conflict
0x00000000…002a
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 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity