← previous blocknext block →recent activity

Analyzing

Block #93,566,062

16 transactions · 16 stateful · 2026-08-06 06:49:40 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

1.13

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,566,062  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x20d33f08…5249

0x34b655…2a6f

8 touches
6 conflicts

0x7a2c83a3…a29a

0x34b655…2a6f

8 touches
6 conflicts

0x98212952…9ba6

0x34b655…2a6f

6 touches
3 conflicts

0x1bf8d2af…d140

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

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

← previous block·next block →recent activity