← previous blocknext block →recent activity

Analyzing

Block #94,990,455

15 transactions · 13 stateful · 2026-08-11 06:30:57 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,990,455  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd2e35622…f491

0x34b655…2a6f

6 touches
3 conflicts

0xf9874e36…beed

0x34b655…2a6f

4 touches
1 conflict

0x0a0cecef…4ed0

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2dff59d9…f5e6

0x34b655…2a6f

4 touches
1 conflict

0x35b4b01c…41f1

0x34b655…2a6f

4 touches
1 conflict

0x939cdd56…00c8

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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 0xd2e3562276…b0f491

← previous block·next block →recent activity