← previous blocknext block →recent activity

Analyzing

Block #86,845,790

26 transactions · 23 stateful · 2026-07-10 13:16:54 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,845,790  ·  26 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

6 touches
3 conflicts

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc788862c…c259

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xec7fe04a…3c56

0x34b655…2a6f

4 touches
1 conflict

0xf2f4727d…cdb7

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity