← previous blocknext block →recent activity

Analyzing

Block #93,362,665

17 transactions · 17 stateful · 2026-08-05 13:47:08 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,362,665  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe800c10b…f5e7

0x34b655…2a6f

8 touches
6 conflicts

0x76736068…b82d

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x79f335e3…93aa

0x34b655…2a6f

4 touches
1 conflict

0x861e5aef…d32c

0x34b655…2a6f

4 touches
1 conflict

0xa60eabc0…9f8c

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xe800c10b68…0df5e7

← previous block·next block →recent activity