← previous blocknext block →recent activity
Analyzing
Block #85,137,234
38 transactions · 27 stateful · 2026-07-02 15:16:28 UTC
Parallelism
89/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,137,234 · 38 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
1w03w14w25w07w08w010w011w115w016w317w126w128w129w231w232w334w035w136w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38b5b2ce…c5bb
0xfa32f9…f3f0
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x605d48ee…ac1e
0xd32edf…ff58
5 touches
3 conflicts
0x40e2d65d…2a35
0x3bd359…433a
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: 0xfa32f9ec…fef3f0
3 conflicts on slot 0x38b5b2ceac…4cc5bb
Audit this contract →
← previous block·next block →recent activity