← previous blocknext block →recent activity
Analyzing
Block #85,351,692
35 transactions · 23 stateful · 2026-07-03 15:04:55 UTC
Parallelism
89/100
Blocked
39%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,351,692 · 35 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
1w02w06w09w011w112w115w016w117w222w126w027w128w230w333w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x25aa9d20…2f62
0xd32edf…ff58
5 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
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: 0x04fdeac2…f747d7
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity