← previous blocknext block →recent activity

Analyzing

Block #93,511,026

16 transactions · 14 stateful · 2026-08-06 02:13:01 UTC

Parallelism

88/100

Blocked

36%

Avg conflicts / tx

0.31

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,511,026  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd79c9727…1233

0x34b655…2a6f

4 touches
1 conflict

0xed697895…3bf6

0x99c7a7…8bf0

4 touches
1 conflict

0x8454e259…1300

0x99c7a7…8bf0

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x4b39e22c…60e5

0x754704…b603

4 touches
1 conflict

0x303ace4f…eae8

0x754704…b603

4 touches
1 conflict

0x0e854949…baa7

0x754704…b603

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

1 conflict on slot 0xd79c972734…f71233

← previous block·next block →recent activity