← previous blocknext block →recent activity

Analyzing

Block #93,370,347

21 transactions · 20 stateful · 2026-08-05 14:25:45 UTC

Parallelism

71/100

Blocked

45%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,370,347  ·  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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xf1040e31…bfff

0x34b655…2a6f

8 touches
6 conflicts

0x2fd12b6c…02cc

0x34b655…2a6f

6 touches
3 conflicts

0x24b08f9c…e594

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x1515b23d…24af

0x34b655…2a6f

6 touches
3 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0x8ec95f2b…f4d7

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