← previous blocknext block →recent activity

Analyzing

Block #74,644,958

22 transactions · 17 stateful · 2026-05-15 00:37:03 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,644,958  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x25c66f9f…97fe

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x78eb0de5…1db2

0x01bff4…1071

2 touches
0 conflicts

0x33018431…8f5c

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5e

0x188d58…ea8e

2 touches
0 conflicts

0x703b861a…cbe3

0x188d58…ea8e

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: 0xd32edf66…9fff58

21 conflicts on slot 0x25c66f9f9b…ca97fe

← previous block·next block →recent activity