← previous blocknext block →recent activity

Analyzing

Block #93,671,819

17 transactions · 16 stateful · 2026-08-06 15:41:19 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,671,819  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x51232c8c…f30c

0xe52b14…7230

8 touches
6 conflicts

0xa6e37efb…afc0

0xe52b14…7230

8 touches
6 conflicts

0xa6e37efb…afc2

0xe52b14…7230

8 touches
6 conflicts

0xf79df061…e005

0xe52b14…7230

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x0b0c2e8d…c1b8

0xe52b14…7230

8 touches
6 conflicts

0xe7650c8f…2958

0xe52b14…7230

7 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 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: 0xe52b1424…bb7230

6 conflicts on slot 0x51232c8c1f…6df30c

← previous block·next block →recent activity