← previous blocknext block →recent activity
Analyzing
Block #85,134,947
33 transactions · 23 stateful · 2026-07-02 15:01:12 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,134,947 · 33 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
2w03w15w06w07w18w210w317w119w020w121w222w326w227w130w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
6 touches
3 conflicts
0x1ed3cf97…88b9
0xd32edf…ff58
5 touches
3 conflicts
0x0b9aba7b…d015
0xa6afd3…d132
5 touches
3 conflicts
0x25e3730b…24a9
0x34b655…2a6f
4 touches
1 conflict
0x75edee02…bd4d
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity