← previous blocknext block →recent activity

Analyzing

Block #74,454,339

16 transactions · 11 stateful · 2026-05-14 03:20:22 UTC

Parallelism

75/100

Blocked

45%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,454,339  ·  16 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

0xa25ed412…0d4e

0xd32edf…ff58

7 touches
6 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7425a853…a582

0x34b655…2a6f

4 touches
1 conflict

0x8cc18498…ce7e

0x34b655…2a6f

4 touches
1 conflict

0x44d7acbf…e67d

0x1b6862…e19c

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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

6 conflicts on slot 0xa25ed41271…2c0d4e

← previous block·next block →recent activity