← previous blocknext block →recent activity

Analyzing

Block #85,131,088

28 transactions · 19 stateful · 2026-07-02 14:35:26 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.32

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,131,088  ·  28 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x04fdea…47d7

6 touches
3 conflicts

0xe1791476…927a

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x7a12283f…b18a

0x69df8a…6292

2 touches
0 conflicts

0x28fabe28…c336

0x754704…b603

2 touches
0 conflicts

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