← previous blocknext block →recent activity

Analyzing

Block #86,695,001

20 transactions · 17 stateful · 2026-07-09 20:29:23 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

0.75

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,695,001  ·  20 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

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x1535d171…c68b

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6c484151…cb14

0x34b655…2a6f

4 touches
1 conflict

0x6f900be0…cd6e

0x34b655…2a6f

4 touches
1 conflict

0x70ff9262…8d80

0x34b655…2a6f

4 touches
1 conflict

0xa523c16d…15cd

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

6 conflicts on slot 0x92385428ad…dc6941

← previous block·next block →recent activity