← previous blocknext block →recent activity

Analyzing

Block #93,345,214

19 transactions · 19 stateful · 2026-08-05 12:19:23 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.26

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,345,214  ·  19 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

0xfed09e59…a493

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xefbb81c0…8474

0x34b655…2a6f

6 touches
3 conflicts

0x28f324ed…9db7

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5317

0x34b655…2a6f

4 touches
1 conflict

0x952f1f66…7fc1

0x34b655…2a6f

4 touches
1 conflict

0xa849dc37…4fb8

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 0xfed09e59c7…d6a493

← previous block·next block →recent activity