← previous blocknext block →recent activity

Analyzing

Block #85,136,269

21 transactions · 17 stateful · 2026-07-02 15:10:01 UTC

Parallelism

57/100

Blocked

53%

Avg conflicts / tx

1.86

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #85,136,269  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x26a197a1…c829

0x34b655…2a6f

4 touches
1 conflict

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0x29deea98…7b5e

0x34b655…2a6f

4 touches
1 conflict

0x366f651e…6100

0x34b655…2a6f

4 touches
1 conflict

0x43e2eda1…396f

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity