← previous blocknext block →recent activity

Analyzing

Block #94,373,359

14 transactions · 10 stateful · 2026-08-09 02:40:51 UTC

Parallelism

86/100

Blocked

20%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #94,373,359  ·  14 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

0x9a89094e…f5b2

0x34b655…2a6f

4 touches
1 conflict

0x9d6946b4…7f4e

0x34b655…2a6f

4 touches
1 conflict

0x4b76146e…0dcb

0x34b655…2a6f

4 touches
1 conflict

0xb44551a3…bf95

0x34b655…2a6f

4 touches
1 conflict

0xba18c5ae…866a

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0x33f54bd6…9ac3

0x34b655…2a6f

4 touches
1 conflict

0x283ecbfb…d3ed

0x34b655…2a6f

2 touches
0 conflicts

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 0x9a89094e2b…f6f5b2

← previous block·next block →recent activity