← previous blocknext block →recent activity

Analyzing

Block #94,317,785

18 transactions · 18 stateful · 2026-08-08 21:58:01 UTC

Parallelism

72/100

Blocked

39%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,317,785  ·  18 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

0xf28a9fc2…05e4

0x34b655…2a6f

6 touches
3 conflicts

0xe3e6c02a…d3d4

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x11b69a7e…334e

0xee8c0e…1242

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x8b79405f…10a2

0x34b655…2a6f

4 touches
1 conflict

0x8d3e8f8c…8de4

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 0xf28a9fc232…c905e4

← previous block·next block →recent activity