← previous blocknext block →recent activity

Analyzing

Block #86,445,502

29 transactions · 19 stateful · 2026-07-08 16:39:20 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,445,502  ·  29 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8590b692…b267

0x34b655…2a6f

6 touches
3 conflicts

0xf5ca1a24…fc49

0x34b655…2a6f

4 touches
1 conflict

0x1aaf4996…65ec

0x34b655…2a6f

4 touches
1 conflict

0x31d2c775…b3b9

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5317

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5318

0x34b655…2a6f

4 touches
1 conflict

0x65e795ca…0320

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