← previous blocknext block →recent activity

Analyzing

Block #93,267,183

21 transactions · 20 stateful · 2026-08-05 05:47:04 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,267,183  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x0de8f3e9…a865

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x7a12283f…b18a

0x2b46c0…1669

4 touches
1 conflict

0xcfe06a18…b5b5

0x2b46c0…1669

4 touches
1 conflict

0xd8fd2add…50fc

0x2b46c0…1669

4 touches
1 conflict

0x1b77e6f7…53d7

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

3 conflicts on slot 0x0de8f3e9aa…fda865

← previous block·next block →recent activity