← previous blocknext block →recent activity

Analyzing

Block #74,402,379

12 transactions · 11 stateful · 2026-05-13 21:34:31 UTC

Parallelism

75/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,402,379  ·  12 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

0xc3aacf13…6b3d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe181f491…f4e3

0x34b655…2a6f

4 touches
1 conflict

0x9b36f19f…fa5a

0x34b655…2a6f

4 touches
1 conflict

0x72a152dd…9ddb

0x16f70c…c3dd

2 touches
0 conflicts

0x00000000…00c9

0x34b655…2a6f

2 touches
0 conflicts

0x037849a8…fa88

0x34b655…2a6f

2 touches
0 conflicts

0x037849a8…fa8d

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

1 conflict on slot 0xc3aacf13f1…5d6b3d

← previous block·next block →recent activity