← previous blocknext block →recent activity

Analyzing

Block #93,309,168

17 transactions · 15 stateful · 2026-08-05 09:18:10 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,309,168  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xb9834665…e363

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x2c2db8e9…fdc7

0x34b655…2a6f

4 touches
1 conflict

0x31519d10…f76b

0x34b655…2a6f

4 touches
1 conflict

0x45ea7a97…bbb3

0x34b655…2a6f

4 touches
1 conflict

0x52cf5603…ca01

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 0xca841faae5…71486a

← previous block·next block →recent activity