← previous blocknext block →recent activity

Analyzing

Block #93,678,588

24 transactions · 21 stateful · 2026-08-06 16:15:21 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,678,588  ·  24 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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x428b6e5b…8909

0x34b655…2a6f

6 touches
3 conflicts

0xf4c9a0df…dcd5

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x1e737223…2278

0x34b655…2a6f

4 touches
1 conflict

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity