← previous blocknext block →recent activity

Analyzing

Block #93,238,663

13 transactions · 10 stateful · 2026-08-05 03:23:40 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,238,663  ·  13 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

0xebac0f82…a49c

0x34b655…2a6f

6 touches
3 conflicts

0x775a8ad3…8307

0x34b655…2a6f

4 touches
1 conflict

0x810a3aa2…0227

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x9fbc6a76…9c29

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xe28e89d1…0cf0

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

3 conflicts on slot 0xebac0f82ec…86a49c

← previous block·next block →recent activity