← previous blocknext block →recent activity

Analyzing

Block #86,611,519

15 transactions · 14 stateful · 2026-07-09 11:10:43 UTC

Parallelism

47/100

Blocked

64%

Avg conflicts / tx

1.73

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,611,519  ·  15 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

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x94ba9c4a…41d8

0x34b655…2a6f

6 touches
3 conflicts

0x7a6681a8…c81c

0x34b655…2a6f

4 touches
1 conflict

0x7b3da897…b268

0x34b655…2a6f

4 touches
1 conflict

0x7ce93f3d…b70e

0x34b655…2a6f

4 touches
1 conflict

0x9c7d2e4b…499b

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 0xf3d10975b0…050d07

← previous block·next block →recent activity