← previous blocknext block →recent activity

Analyzing

Block #93,290,587

19 transactions · 15 stateful · 2026-08-05 07:44:44 UTC

Parallelism

84/100

Blocked

40%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,290,587  ·  19 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

0x185eacc9…9e18

0x34b655…2a6f

4 touches
1 conflict

0x38bdc5d3…a632

0x34b655…2a6f

4 touches
1 conflict

0x4bc1abab…5874

0x34b655…2a6f

4 touches
1 conflict

0x6135a6eb…c6bb

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7aae9795…06ed

0x34b655…2a6f

4 touches
1 conflict

0x861e5aef…d32c

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd6

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 0x185eacc944…659e18

← previous block·next block →recent activity