← previous blocknext block →recent activity

Analyzing

Block #93,343,363

23 transactions · 18 stateful · 2026-08-05 12:10:04 UTC

Parallelism

83/100

Blocked

28%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,343,363  ·  23 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xf9e23360…8ef7

0x34b655…2a6f

6 touches
3 conflicts

0x18978822…2623

0x34b655…2a6f

4 touches
1 conflict

0x2c539d94…b63a

0x34b655…2a6f

4 touches
1 conflict

0x3b56f79b…310f

0x34b655…2a6f

4 touches
1 conflict

0x7224bc33…65c2

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x840d3ab7…c8c4

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 0x482471adbb…39122f

← previous block·next block →recent activity