← previous blocknext block →recent activity

Analyzing

Block #86,499,319

15 transactions · 12 stateful · 2026-07-08 22:39:13 UTC

Parallelism

87/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,499,319  ·  15 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x62d6e82b…a750

0x34b655…2a6f

4 touches
1 conflict

0x9f6b474b…5d0f

0x34b655…2a6f

4 touches
1 conflict

0x32ac8928…1b7a

0x34b655…2a6f

4 touches
1 conflict

0x7c6a17fa…e95d

0x34b655…2a6f

4 touches
1 conflict

0xc16a09bc…b756

0x34b655…2a6f

4 touches
1 conflict

0xe1d1f14d…3ffb

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x62d6e82b38…66a750

← previous block·next block →recent activity