← previous blocknext block →recent activity

Analyzing

Block #85,964,984

18 transactions · 17 stateful · 2026-07-06 11:10:38 UTC

Parallelism

56/100

Blocked

47%

Avg conflicts / tx

1.72

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,964,984  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x01414ad2…98ec

0x34b655…2a6f

4 touches
1 conflict

0x0a6f5e37…6c3c

0x34b655…2a6f

4 touches
1 conflict

0x172b0de5…980b

0x34b655…2a6f

4 touches
1 conflict

0x32adb2c4…32c5

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4abfb389…18f4

0x34b655…2a6f

4 touches
1 conflict

0x5e0b8bbe…377b

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity