← previous blocknext block →recent activity

Analyzing

Block #74,391,210

10 transactions · 9 stateful · 2026-05-13 20:20:07 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,391,210  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb8e56e6d…2b20

0x065c9d…c394

6 touches
3 conflicts

0x29552994…4328

0x065c9d…c394

5 touches
3 conflicts

0xc68b83b8…7afd

0x065c9d…c394

4 touches
1 conflict

0x47d9f48e…d757

0x065c9d…c394

3 touches
1 conflict

0x23138e6e…1c34

0x065c9d…c394

3 touches
1 conflict

0xd613dd7b…eea0

0x065c9d…c394

3 touches
1 conflict

0x8d7d9c65…8ad6

0x065c9d…c394

2 touches
0 conflicts

0x8dbb9fd1…8cce

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

3 conflicts on slot 0xb8e56e6dbc…482b20

← previous block·next block →recent activity