← previous blocknext block →recent activity

Analyzing

Block #93,539,100

25 transactions · 20 stateful · 2026-08-06 04:34:08 UTC

Parallelism

72/100

Blocked

45%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,539,100  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x1730ab3c…ce37

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xabd0bcfc…64e2

0x34b655…2a6f

10 touches
10 conflicts

0x8743e1ba…8331

0x34b655…2a6f

6 touches
3 conflicts

0x8d175439…fb79

0x34b655…2a6f

4 touches
1 conflict

0x91f7608d…d318

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eeb

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

10 conflicts on slot 0x1730ab3ce5…2dce37

← previous block·next block →recent activity