← previous blocknext block →recent activity
Analyzing
Block #85,993,307
29 transactions · 23 stateful · 2026-07-06 14:19:52 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,993,307 · 29 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
1w03w16w07w18w29w110w011w112w013w014w116w117w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd90a674b…29f7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xade0e240…1581
0xd32edf…ff58
5 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x2c506459…5351
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xd90a674bde…9a29f7
Audit this contract →
← previous block·next block →recent activity