← previous blocknext block →recent activity

Analyzing

Block #86,487,027

25 transactions · 21 stateful · 2026-07-08 21:17:11 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,487,027  ·  25 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

0x080ec687…da80

0x34b655…2a6f

6 touches
3 conflicts

0xb624d2ea…8c87

0x34b655…2a6f

6 touches
3 conflicts

0x9fb55ee7…8ecc

0xa6afd3…d132

4 touches
1 conflict

0x2493f8e8…f853

0x34b655…2a6f

4 touches
1 conflict

0x8b87ece6…3353

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7212

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0x080ec68796…07da80

← previous block·next block →recent activity