← previous blocknext block →recent activity

Analyzing

Block #93,441,097

22 transactions · 22 stateful · 2026-08-05 20:21:28 UTC

Parallelism

64/100

Blocked

55%

Avg conflicts / tx

1.77

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,441,097  ·  22 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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0x80656e3b…9240

0x34b655…2a6f

10 touches
10 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

6 touches
3 conflicts

0x74f95963…01a2

0x34b655…2a6f

6 touches
3 conflicts

0x3fff7ccd…5a48

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4a5956ef…e226

0x34b655…2a6f

4 touches
1 conflict

0x5e0b8bbe…377b

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity