← previous blocknext block →recent activity

Analyzing

Block #86,292,296

24 transactions · 17 stateful · 2026-07-07 23:35:50 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,292,296  ·  24 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x89750670…2dea

0xa6afd3…d132

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0eeb2a30…6909

0x34b655…2a6f

4 touches
1 conflict

0x42bb0ac5…6b33

0x34b655…2a6f

4 touches
1 conflict

0x69ce640b…884a

0x34b655…2a6f

4 touches
1 conflict

0xc5a1b2fe…5369

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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

← previous block·next block →recent activity