← previous blocknext block →recent activity

Analyzing

Block #85,160,069

22 transactions · 20 stateful · 2026-07-02 17:48:34 UTC

Parallelism

68/100

Blocked

45%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,160,069  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0x04fdea…47d7

14 touches
21 conflicts

0x7d1d4626…7bc0

0x40c49f…2af0

4 touches
1 conflict

0xdb6a3a62…f5dd

0x40c49f…2af0

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xf5310ef7…485a

0x40c49f…2af0

2 touches
0 conflicts

0x213ee207…a151

0x69df8a…6292

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: 0x04fdeac2…f747d7

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity