← previous blocknext block →recent activity

Analyzing

Block #93,075,056

17 transactions · 16 stateful · 2026-08-04 13:40:13 UTC

Parallelism

76/100

Blocked

56%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,075,056  ·  17 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…6426

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xa69ba9e8…e56a

0x34b655…2a6f

6 touches
3 conflicts

0x94de4d05…ad01

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xa457c06e…2f06

0x34b655…2a6f

4 touches
1 conflict

0xac3e4969…39e9

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

← previous block·next block →recent activity