← previous blocknext block →recent activity

Analyzing

Block #74,456,584

22 transactions · 13 stateful · 2026-05-14 03:35:22 UTC

Parallelism

91/100

Blocked

23%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,456,584  ·  22 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x148cc724…aa90

0x065c9d…c394

2 touches
0 conflicts

0x1df75cfb…2b26

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xa976d19d…543c

0x065c9d…c394

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity