← previous blocknext block →recent activity

Analyzing

Block #74,722,022

20 transactions · 16 stateful · 2026-05-15 09:11:01 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,722,022  ·  20 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

0x1cf3937e…ce07

0xd32edf…ff58

11 touches
15 conflicts

0x56a919c4…ab49

0xe7cd86…c82d

4 touches
1 conflict

0x56a919c4…ab49

0x01bff4…1071

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x703b861a…cbe3

0x188d58…ea8e

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

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

15 conflicts on slot 0x1cf3937e74…bece07

← previous block·next block →recent activity