← previous blocknext block →recent activity

Analyzing

Block #93,551,273

20 transactions · 16 stateful · 2026-08-06 05:35:20 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,551,273  ·  20 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x89678d1b…463e

0xa6afd3…d132

6 touches
3 conflicts

0x69a45f39…39aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x8218911e…3bed

0x34b655…2a6f

4 touches
1 conflict

0x99c5409a…25b7

0x34b655…2a6f

4 touches
1 conflict

0x9a6bc012…7495

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

← previous block·next block →recent activity