← previous blocknext block →recent activity

Analyzing

Block #93,578,736

19 transactions · 18 stateful · 2026-08-06 07:53:23 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.42

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,578,736  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb1b58b33…874f

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xb4ed8bd9…4a8f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x91855e…ac7e

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 0x52b477bcb8…5d7ccf

← previous block·next block →recent activity