← previous blocknext block →recent activity

Analyzing

Block #86,337,890

20 transactions · 19 stateful · 2026-07-08 04:40:29 UTC

Parallelism

70/100

Blocked

37%

Avg conflicts / tx

0.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,337,890  ·  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

0xda46a376…f6a6

0x34b655…2a6f

6 touches
3 conflicts

0x87ee379a…cd9e

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4beb0d8d…2a68

0x34b655…2a6f

4 touches
1 conflict

0x4bfdcd51…9b58

0x34b655…2a6f

4 touches
1 conflict

0xb0cd8fbb…eb3b

0x34b655…2a6f

4 touches
1 conflict

0xc69edfa9…70e1

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 0xda46a376d7…59f6a6

← previous block·next block →recent activity