← previous blocknext block →recent activity

Analyzing

Block #86,702,832

20 transactions · 17 stateful · 2026-07-09 21:21:38 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,702,832  ·  20 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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x63c900f4…2600

0x34b655…2a6f

6 touches
3 conflicts

0x1951ee47…540f

0x34b655…2a6f

4 touches
1 conflict

0x3483ab79…8ed3

0x34b655…2a6f

4 touches
1 conflict

0x387231f6…6b29

0x34b655…2a6f

4 touches
1 conflict

0x3a2a8323…3f40

0x34b655…2a6f

4 touches
1 conflict

0x822c75ed…0870

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