← previous blocknext block →recent activity

Analyzing

Block #74,937,925

11 transactions · 7 stateful · 2026-05-16 09:12:21 UTC

Parallelism

82/100

Blocked

14%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,937,925  ·  11 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

0xa221f58f…b32c

0x065c9d…c394

4 touches
1 conflict

0xaa03094a…d944

0x065c9d…c394

3 touches
1 conflict

0xc692fc08…0aab

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0519dbb7…f26b

0x065c9d…c394

2 touches
0 conflicts

0x52c4e3d4…57a4

0x065c9d…c394

2 touches
0 conflicts

0x65d3f27b…83b5

0x065c9d…c394

2 touches
0 conflicts

0x9715b5d4…d0b1

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

1 conflict on slot 0xa221f58ff7…f9b32c

← previous block·next block →recent activity