← previous blocknext block →recent activity

Analyzing

Block #93,235,862

17 transactions · 16 stateful · 2026-08-05 03:09:35 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

1.53

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,235,862  ·  17 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x33dde6d3…c08b

0x34b655…2a6f

8 touches
6 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0xb762713c…bcd7

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x2fd12b6c…02cc

0x34b655…2a6f

6 touches
3 conflicts

0xfed09e59…a493

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity