← previous blocknext block →recent activity

Analyzing

Block #74,457,335

22 transactions · 16 stateful · 2026-05-14 03:40:23 UTC

Parallelism

91/100

Blocked

6%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,457,335  ·  22 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0ef74796…cd18

0x0a3323…0a3c

2 touches
0 conflicts

0xdeaab6a3…ccad

0x0a3323…0a3c

2 touches
0 conflicts

0x10a191e0…3056

0x34b655…2a6f

2 touches
0 conflicts

0x1c389468…6b0e

0x34b655…2a6f

2 touches
0 conflicts

0x8d13ecc1…980f

0x34b655…2a6f

2 touches
0 conflicts

0x97d5efed…1aa4

0x34b655…2a6f

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity