← previous blocknext block →recent activity

Analyzing

Block #94,718,830

13 transactions · 11 stateful · 2026-08-10 07:43:14 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #94,718,830  ·  13 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

0xd4f19f6e…68c9

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x4560e5a8…b741

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5d1ac445…5233

0x34b655…2a6f

4 touches
1 conflict

0x70cfbacf…5c46

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd6

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd7

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

1 conflict on slot 0xd4f19f6e0d…7868c9

← previous block·next block →recent activity