← previous blocknext block →recent activity

Analyzing

Block #93,931,339

26 transactions · 20 stateful · 2026-08-07 13:26:28 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.73

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,931,339  ·  26 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

8 touches
6 conflicts

0x00000000…0002

0x91855e…ac7e

6 touches
3 conflicts

0xebac0f82…a49c

0x34b655…2a6f

6 touches
3 conflicts

0x45ef9175…5ab2

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xa3f6f7c8…2436

0x34b655…2a6f

4 touches
1 conflict

0xa86351b8…2c5a

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity