← previous blocknext block →recent activity

Analyzing

Block #86,487,272

27 transactions · 22 stateful · 2026-07-08 21:18:49 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,487,272  ·  27 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

0xd99b3b64…1c95

0x34b655…2a6f

8 touches
6 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

6 touches
3 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x90ca0de6…efee

0x34b655…2a6f

6 touches
3 conflicts

0x9f40a209…1193

0x34b655…2a6f

6 touches
3 conflicts

0xa7e2f1b7…7e6f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 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

6 conflicts on slot 0xd99b3b6441…7a1c95

← previous block·next block →recent activity