← previous blocknext block →recent activity

Analyzing

Block #74,762,096

25 transactions · 11 stateful · 2026-05-15 13:39:06 UTC

Parallelism

84/100

Blocked

36%

Avg conflicts / tx

0.28

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,762,096  ·  25 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…003d

0x065c9d…c394

8 touches
6 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x8a06e274…9522

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xd5cc32cb…4d5a

0x065c9d…c394

3 touches
1 conflict

0x8e7c62ec…2fd5

0x065c9d…c394

3 touches
1 conflict

0x56c6a014…3aaa

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity