← previous blocknext block →recent activity

Analyzing

Block #74,654,519

11 transactions · 9 stateful · 2026-05-15 01:40:49 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,654,519  ·  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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xf09d9474…aad0

0x065c9d…c394

4 touches
1 conflict

0xf96ece64…fcab

0x065c9d…c394

3 touches
1 conflict

0x5549b676…b4f7

0x065c9d…c394

3 touches
1 conflict

0x1dfd73e7…547b

0x065c9d…c394

2 touches
0 conflicts

0x3e55f9e3…11d0

0x065c9d…c394

2 touches
0 conflicts

0x52b33beb…e754

0x065c9d…c394

2 touches
0 conflicts

0xc5e1b014…f0f3

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity