← previous blocknext block →recent activity

Analyzing

Block #74,906,611

10 transactions · 7 stateful · 2026-05-16 05:43:26 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,906,611  ·  10 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

0xd765e9d3…8787

0x065c9d…c394

3 touches
1 conflict

0x264030bf…7909

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x6b0f15fc…2e68

0x000000…8ba3

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xc2756ff4…7cb8

0x065c9d…c394

2 touches
0 conflicts

0xcef8585d…826c

0x065c9d…c394

2 touches
0 conflicts

0xe9344c4c…f9a5

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 0xd765e9d3cf…6b8787

← previous block·next block →recent activity