← previous blocknext block →recent activity

Analyzing

Block #85,354,744

23 transactions · 20 stateful · 2026-07-03 15:25:11 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,354,744  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xf5310ef7…485a

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x126b8491…488d

0x34b655…2a6f

4 touches
1 conflict

0x342a12bc…c045

0x34b655…2a6f

4 touches
1 conflict

0x4dcc3c37…317c

0x34b655…2a6f

4 touches
1 conflict

0x83f3d320…fb59

0x34b655…2a6f

4 touches
1 conflict

0x8d24fe06…31f4

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity