← previous blocknext block →recent activity

Analyzing

Block #86,234,405

20 transactions · 18 stateful · 2026-07-07 17:09:25 UTC

Parallelism

70/100

Blocked

39%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,234,405  ·  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

0xf9e23360…8ef7

0x34b655…2a6f

8 touches
6 conflicts

0x52d13e43…a61d

0x34b655…2a6f

6 touches
3 conflicts

0x30ae635d…5e67

0x34b655…2a6f

6 touches
3 conflicts

0x7754e0f5…d02e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xec0e0220…cb90

0x34b655…2a6f

6 touches
3 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0x1b159f3d…9163

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

6 conflicts on slot 0xf9e23360ff…e88ef7

← previous block·next block →recent activity