← previous blocknext block →recent activity

Analyzing

Block #93,579,341

17 transactions · 15 stateful · 2026-08-06 07:56:25 UTC

Parallelism

88/100

Blocked

20%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,579,341  ·  17 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

0xd676e291…3ecf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x24b6091e…d294

0x34b655…2a6f

2 touches
0 conflicts

0x4a5956ef…e226

0x34b655…2a6f

2 touches
0 conflicts

0x5e0b8bbe…377b

0x34b655…2a6f

2 touches
0 conflicts

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 0xd676e29175…2b3ecf

← previous block·next block →recent activity