← previous blocknext block →recent activity

Analyzing

Block #74,762,975

10 transactions · 9 stateful · 2026-05-15 13:45:00 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.3

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,762,975  ·  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

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x4baf3fa7…cb9d

0x065c9d…c394

2 touches
0 conflicts

0xad436b12…f632

0x1111b3…4111

2 touches
0 conflicts

0xb7c8652f…ebce

0x1111b3…4111

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 0xfcb7b8b239…6bebb3

← previous block·next block →recent activity