← previous blocknext block →recent activity

Analyzing

Block #93,549,805

21 transactions · 17 stateful · 2026-08-06 05:27:57 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,549,805  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x80656e3b…9240

0x34b655…2a6f

8 touches
6 conflicts

0x69a45f39…39aa

0x34b655…2a6f

8 touches
6 conflicts

0xd676e291…3ecf

0x34b655…2a6f

6 touches
3 conflicts

0x99c5409a…25b7

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4e8c4408…d37a

0x34b655…2a6f

4 touches
1 conflict

0x4e8c4408…d37b

0x34b655…2a6f

4 touches
1 conflict

0x6719a767…9d62

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 0x80656e3b9f…e39240

← previous block·next block →recent activity