← previous blocknext block →recent activity

Analyzing

Block #94,750,009

20 transactions · 19 stateful · 2026-08-10 10:21:12 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,750,009  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00ddbbf2…4588

0x34b655…2a6f

4 touches
1 conflict

0x24ca1902…7a87

0x34b655…2a6f

4 touches
1 conflict

0x267d92a4…197c

0x34b655…2a6f

4 touches
1 conflict

0x45273c2a…5ae2

0x34b655…2a6f

4 touches
1 conflict

0x4f1ad4b4…e00a

0x34b655…2a6f

4 touches
1 conflict

0x6a4c23bd…3d81

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity