← previous blocknext block →recent activity

Analyzing

Block #74,456,969

24 transactions · 18 stateful · 2026-05-14 03:37:56 UTC

Parallelism

75/100

Blocked

56%

Avg conflicts / tx

0.96

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,456,969  ·  24 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

0xc9d4997e…64d7

0xd32edf…ff58

11 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xb8228d38…3953

0x34b655…2a6f

6 touches
3 conflicts

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xc08384da…ecb7

0x34b655…2a6f

4 touches
1 conflict

0x4ee6f153…3ef4

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

15 conflicts on slot 0xc9d4997e7f…0c64d7

← previous block·next block →recent activity