← previous blocknext block →recent activity

Analyzing

Block #93,234,382

21 transactions · 18 stateful · 2026-08-05 03:02:08 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,234,382  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x0759c8f2…8408

0x34b655…2a6f

6 touches
3 conflicts

0x2f675ab5…6407

0x34b655…2a6f

4 touches
1 conflict

0x2ffa0115…ed47

0x34b655…2a6f

4 touches
1 conflict

0x45b3c66c…b788

0x34b655…2a6f

4 touches
1 conflict

0x56e254bc…1215

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 0x737acb7813…fafce8

← previous block·next block →recent activity