← previous blocknext block →recent activity

Analyzing

Block #93,749,137

21 transactions · 19 stateful · 2026-08-06 22:10:02 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,749,137  ·  21 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

0xb1b58b33…874f

0x34b655…2a6f

8 touches
6 conflicts

0x2fd12b6c…02cc

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x4b503452…1b1f

0x34b655…2a6f

6 touches
3 conflicts

0x4bfdcd51…9b58

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xa03c2a35…52e6

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 0xb1b58b3385…e4874f

← previous block·next block →recent activity