← previous blocknext block →recent activity

Analyzing

Block #86,812,941

20 transactions · 16 stateful · 2026-07-10 09:37:09 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,812,941  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb06917e8…6985

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8f9b6254…f564

0x34b655…2a6f

4 touches
1 conflict

0x98862f54…62ca

0x34b655…2a6f

4 touches
1 conflict

0xb0446875…2b96

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