← previous blocknext block →recent activity

Analyzing

Block #93,932,073

18 transactions · 18 stateful · 2026-08-07 13:30:10 UTC

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.44

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,932,073  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xfc3d5171…8357

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0x30932529…5ab2

0x34b655…2a6f

9 touches
10 conflicts

0x948836ff…59ab

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0xe5dabb7e…0e82

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

15 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity