← previous blocknext block →recent activity

Analyzing

Block #86,231,353

20 transactions · 17 stateful · 2026-07-07 16:49:01 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,231,353  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x839c0c71…bada

0x34b655…2a6f

6 touches
3 conflicts

0x3a7fb5b5…f0e5

0x34b655…2a6f

4 touches
1 conflict

0x5e4d6834…2898

0x34b655…2a6f

4 touches
1 conflict

0x5f7a3592…a023

0x34b655…2a6f

4 touches
1 conflict

0x68c07cb9…ae14

0x34b655…2a6f

4 touches
1 conflict

0x6db97e95…8353

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity