← previous blocknext block →recent activity

Analyzing

Block #93,669,768

23 transactions · 23 stateful · 2026-08-06 15:31:01 UTC

Parallelism

70/100

Blocked

39%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,669,768  ·  23 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x454cdf57…aebc

0x34b655…2a6f

4 touches
1 conflict

0x48717abe…be13

0x34b655…2a6f

4 touches
1 conflict

0x5aed1bd2…7afa

0x34b655…2a6f

4 touches
1 conflict

0x7150753f…7e32

0x34b655…2a6f

4 touches
1 conflict

0x7c1d804e…835c

0x34b655…2a6f

4 touches
1 conflict

0x7fa44fe8…484e

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 0xca841faae5…71486a

← previous block·next block →recent activity