← previous blocknext block →recent activity

Analyzing

Block #86,221,291

19 transactions · 17 stateful · 2026-07-07 15:41:50 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.32

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,221,291  ·  19 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

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x390136d0…5a69

0x34b655…2a6f

6 touches
3 conflicts

0xa4658f5c…b257

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xbbb9fa77…d121

0x34b655…2a6f

6 touches
3 conflicts

0x9966da31…0d0f

0x34b655…2a6f

4 touches
1 conflict

0xb56f0740…7542

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity