← previous blocknext block →recent activity
Analyzing
Block #85,992,386
27 transactions · 20 stateful · 2026-07-06 14:13:43 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,992,386 · 27 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
3w04w15w212w213w314w016w117w024w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xf5310ef7…485a
0x40c49f…2af0
6 touches
3 conflicts
0x5fcb4c60…8775
0x34b655…2a6f
6 touches
3 conflicts
0xd0310a47…24b4
0x40c49f…2af0
6 touches
3 conflicts
0x5768966e…c8f7
0x40c49f…2af0
4 touches
2 conflicts
0x213ee207…a151
0x69df8a…6292
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: 0x40c49f17…d22af0
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity