← previous blocknext block →recent activity

Analyzing

Block #74,352,589

17 transactions · 16 stateful · 2026-05-13 16:03:03 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,352,589  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…0002

0xab3526…fa38

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x38c47502…1005

0x34b655…2a6f

2 touches
0 conflicts

0x5ab1ec63…ac9c

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity