← previous blocknext block →recent activity

Analyzing

Block #86,629,380

20 transactions · 15 stateful · 2026-07-09 13:09:56 UTC

Parallelism

60/100

Blocked

67%

Avg conflicts / tx

1.2

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,629,380  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0xa7013be2…c0a8

0x34b655…2a6f

10 touches
10 conflicts

0x52e69143…95ad

0x065c9d…c394

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x5f251b96…6054

0x34b655…2a6f

4 touches
1 conflict

0x61d6f6e7…87d6

0x34b655…2a6f

4 touches
1 conflict

0x70ff9262…8d80

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity