← previous blocknext block →recent activity

Analyzing

Block #74,443,476

22 transactions · 17 stateful · 2026-05-14 02:08:05 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,443,476  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x728f999a…832f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd89f212d…2bbf

0x34b655…2a6f

4 touches
1 conflict

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0000

0x4d7f22…2fe0

4 touches
1 conflict

0x2484cc15…5afc

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity