← previous blocknext block →recent activity

Analyzing

Block #74,370,297

7 transactions · 6 stateful · 2026-05-13 18:00:52 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,370,297  ·  7 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5151d985…fc0c

0x065c9d…c394

4 touches
1 conflict

0x52034df0…d661

0x065c9d…c394

3 touches
1 conflict

0x393772ad…6627

0x065c9d…c394

2 touches
0 conflicts

0x39474ebd…d51a

0x065c9d…c394

2 touches
0 conflicts

0xcd2c61fc…6746

0x065c9d…c394

2 touches
0 conflicts

0x0872abbe…9c39

0x2a68ba…90c5

2 touches
0 conflicts

0x76e559a4…77fb

0x2a68ba…90c5

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity