← previous blocknext block →recent activity

Analyzing

Block #86,135,074

20 transactions · 18 stateful · 2026-07-07 06:06:13 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,135,074  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x18cf3003…51d1

0x065c9d…c394

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x79b3209b…f766

0x34b655…2a6f

4 touches
1 conflict

0x89999c15…fdac

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xaa2c7f80…2e5b

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity