← previous blocknext block →recent activity

Analyzing

Block #74,766,901

19 transactions · 15 stateful · 2026-05-15 14:11:18 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

1.11

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,766,901  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb9868b52…c77f

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

0xca0fef1c…b548

0x34b655…2a6f

6 touches
3 conflicts

0xdc683230…6df3

0x34b655…2a6f

6 touches
3 conflicts

0x6fef938b…f05a

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

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: 0x34b6552d…112a6f

10 conflicts on slot 0xb9868b5233…c6c77f

← previous block·next block →recent activity