← previous blocknext block →recent activity

Analyzing

Block #93,924,686

18 transactions · 17 stateful · 2026-08-07 12:53:02 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1.22

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,924,686  ·  18 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

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x5a100ac0…96d3

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xa3ed5a09…c6d3

0x34b655…2a6f

6 touches
3 conflicts

0xfb24441a…4183

0x34b655…2a6f

6 touches
3 conflicts

0x056cfe8c…0a8f

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

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 0x482471adbb…39122f

← previous block·next block →recent activity