← previous blocknext block →recent activity

Analyzing

Block #86,101,619

25 transactions · 20 stateful · 2026-07-07 02:22:53 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,101,619  ·  25 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

12 touches
15 conflicts

0x01737532…9b12

0x34b655…2a6f

6 touches
3 conflicts

0xaf498679…7732

0x34b655…2a6f

6 touches
3 conflicts

0xe5eb3c33…0e3a

0x34b655…2a6f

6 touches
3 conflicts

0x77cf3c7b…a722

0x34b655…2a6f

4 touches
1 conflict

0x931619e4…3b17

0x34b655…2a6f

4 touches
1 conflict

0x94dabb65…43a3

0x34b655…2a6f

4 touches
1 conflict

0xac6f24e7…c98b

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity