← previous blocknext block →recent activity

Analyzing

Block #86,849,125

18 transactions · 17 stateful · 2026-07-10 13:39:09 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,849,125  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x3a2a8323…3f40

0x34b655…2a6f

4 touches
1 conflict

0x3d4c0233…20a5

0x34b655…2a6f

4 touches
1 conflict

0x410b84ab…1dbc

0x34b655…2a6f

4 touches
1 conflict

0x6c7b899c…70ff

0x34b655…2a6f

4 touches
1 conflict

0x6c7b899c…7100

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 0x92385428ad…dc6941

← previous block·next block →recent activity