← previous blocknext block →recent activity

Analyzing

Block #74,485,303

10 transactions · 9 stateful · 2026-05-14 06:46:25 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,485,303  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x863b87ad…548c

0xd32edf…ff58

5 touches
3 conflicts

0x2e4c2bfb…330b

0x065c9d…c394

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0003

0x0594c7…a3be

2 touches
0 conflicts

0x00000000…0004

0x0594c7…a3be

2 touches
0 conflicts

0x00000000…0005

0x0594c7…a3be

2 touches
0 conflicts

0x7b59e08e…d4b0

0x0594c7…a3be

2 touches
0 conflicts

0xb504cd7e…5a81

0x0594c7…a3be

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: 0xd32edf66…9fff58

3 conflicts on slot 0x863b87ad9b…f8548c

← previous block·next block →recent activity