← previous blocknext block →recent activity

Analyzing

Block #93,367,204

19 transactions · 17 stateful · 2026-08-05 14:09:57 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,367,204  ·  19 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

0x1cdfe548…d3aa

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xf06fce24…887d

0x34b655…2a6f

6 touches
3 conflicts

0x5ab08865…574c

0x34b655…2a6f

6 touches
3 conflicts

0x254a2653…24ed

0x34b655…2a6f

4 touches
1 conflict

0x2c390858…b1ed

0x34b655…2a6f

4 touches
1 conflict

0x4188cc5f…2d2e

0x34b655…2a6f

4 touches
1 conflict

0x6254804c…a03b

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

3 conflicts on slot 0x1cdfe54872…bcd3aa

← previous block·next block →recent activity