← previous blocknext block →recent activity

Analyzing

Block #93,581,365

14 transactions · 14 stateful · 2026-08-06 08:06:36 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.86

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,581,365  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x52b477bc…7ccf

0x34b655…2a6f

8 touches
6 conflicts

0xd676e291…3ecf

0x34b655…2a6f

6 touches
3 conflicts

0x7a2c83a3…a29a

0x34b655…2a6f

6 touches
3 conflicts

0xf55f12f0…a758

0x34b655…2a6f

4 touches
1 conflict

0x226ae29a…2612

0x34b655…2a6f

4 touches
1 conflict

0x2328941c…84d3

0x34b655…2a6f

4 touches
1 conflict

0x1e56f6b6…5940

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

6 conflicts on slot 0x52b477bcb8…5d7ccf

← previous block·next block →recent activity