← previous blocknext block →recent activity

Analyzing

Block #86,315,915

21 transactions · 17 stateful · 2026-07-08 02:13:41 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,315,915  ·  21 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

0x427c9fc4…5cee

0x34b655…2a6f

10 touches
10 conflicts

0xec0e0220…cb90

0x34b655…2a6f

6 touches
3 conflicts

0xca411fd0…9734

0x34b655…2a6f

6 touches
3 conflicts

0x3bdd71a2…b6eb

0x34b655…2a6f

6 touches
3 conflicts

0x39cc2185…caca

0x34b655…2a6f

4 touches
1 conflict

0x39cc2185…cacb

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

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 0x427c9fc46b…895cee

← previous block·next block →recent activity