← previous blocknext block →recent activity

Analyzing

Block #86,250,169

23 transactions · 18 stateful · 2026-07-07 18:54:47 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,250,169  ·  23 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

0x1526b11f…8b21

0x34b655…2a6f

6 touches
3 conflicts

0xb56f0740…7542

0x34b655…2a6f

6 touches
3 conflicts

0xac33ff75…077b

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xee8237bd…46ad

0x34b655…2a6f

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

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