← previous blocknext block →recent activity

Analyzing

Block #74,346,257

12 transactions · 11 stateful · 2026-05-13 15:21:01 UTC

Parallelism

58/100

Blocked

45%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,346,257  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x2c79950c…953c

0x065c9d…c394

2 touches
0 conflicts

0x3d170b4a…c6be

0x065c9d…c394

2 touches
0 conflicts

0xafb86cc2…01d4

0x065c9d…c394

2 touches
0 conflicts

0xeaf93c4b…69e4

0x065c9d…c394

2 touches
0 conflicts

0xf1730885…141d

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: 0x065c9d28…a9c394

6 conflicts on slot 0xffe431af56…838faa

← previous block·next block →recent activity