← previous blocknext block →recent activity

Analyzing

Block #74,506,497

11 transactions · 9 stateful · 2026-05-14 09:07:53 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,506,497  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x05c3b7fc…dfbd

0x065c9d…c394

2 touches
0 conflicts

0x0bdd2be1…3c04

0x065c9d…c394

2 touches
0 conflicts

0x1ec54820…f01c

0x065c9d…c394

2 touches
0 conflicts

0x283a9549…68d7

0x065c9d…c394

2 touches
0 conflicts

0x4c7cb0b4…9696

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 0x0000000000…00003d

← previous block·next block →recent activity