← previous blocknext block →recent activity

Analyzing

Block #74,359,121

20 transactions · 15 stateful · 2026-05-13 16:46:30 UTC

Parallelism

55/100

Blocked

60%

Avg conflicts / tx

1.85

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,359,121  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf9dc969b…ae48

0x065c9d…c394

3 touches
1 conflict

0xe3fdcd7c…95de

0x065c9d…c394

3 touches
1 conflict

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x9e6af916…1ae3

0x065c9d…c394

2 touches
0 conflicts

0xba34589d…0516

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

36 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity