← previous blocknext block →recent activity

Analyzing

Block #93,666,887

16 transactions · 15 stateful · 2026-08-06 15:16:32 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,666,887  ·  16 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

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd7e839c4…9190

0x34b655…2a6f

4 touches
1 conflict

0xd93edb3f…94ec

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xfaefdbf4…bf65

0x34b655…2a6f

4 touches
1 conflict

0xad3e66be…dccc

0xc8689a…ee79

4 touches
1 conflict

0x68c07cb9…ae14

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 0xc824469a90…af6425

← previous block·next block →recent activity