← previous blocknext block →recent activity

Analyzing

Block #74,460,636

15 transactions · 11 stateful · 2026-05-14 04:02:19 UTC

Parallelism

80/100

Blocked

27%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,460,636  ·  15 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

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0xf59f3a95…99ba

0xd32edf…ff58

3 touches
1 conflict

0x10a191e0…3056

0x34b655…2a6f

2 touches
0 conflicts

0x195b037f…e0f6

0x34b655…2a6f

2 touches
0 conflicts

0x8d13ecc1…980f

0x34b655…2a6f

2 touches
0 conflicts

0x8fdebdb1…d449

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 0xffe431af56…838faa

← previous block·next block →recent activity