← previous blocknext block →recent activity

Analyzing

Block #74,409,600

24 transactions · 14 stateful · 2026-05-13 22:22:37 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,409,600  ·  24 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

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xe527656e…2164

0x139aab…382b

2 touches
0 conflicts

0xe527656e…2165

0x139aab…382b

2 touches
0 conflicts

0x1da1c6cb…bb3f

0x34b655…2a6f

2 touches
0 conflicts

0x44f26cbe…58c2

0x34b655…2a6f

2 touches
0 conflicts

0x71e4ffd1…9beb

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: 0xab35264b…1cfa38

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity