← previous blocknext block →recent activity

Analyzing

Block #74,450,246

13 transactions · 7 stateful · 2026-05-14 02:53:08 UTC

Parallelism

77/100

Blocked

29%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,450,246  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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…003d

0x065c9d…c394

6 touches
3 conflicts

0x34180922…5dc1

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x1c692271…5ae1

0x065c9d…c394

2 touches
0 conflicts

0x309c141e…0e0a

0x065c9d…c394

2 touches
0 conflicts

0xb3455d37…cd21

0x065c9d…c394

2 touches
0 conflicts

0x0872abbe…9c39

0x2a68ba…90c5

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity