← previous blocknext block →recent activity

Analyzing

Block #93,151,445

19 transactions · 18 stateful · 2026-08-04 20:05:09 UTC

Parallelism

47/100

Blocked

56%

Avg conflicts / tx

1.58

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #93,151,445  ·  19 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xb9834665…e363

0x34b655…2a6f

10 touches
10 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

8 touches
6 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xebac0f82…a49c

0x34b655…2a6f

6 touches
3 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

6 touches
3 conflicts

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

10 conflicts on slot 0xb983466539…cee363

← previous block·next block →recent activity