← previous blocknext block →recent activity

Analyzing

Block #74,414,381

6 transactions · 6 stateful · 2026-05-13 22:54:23 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,414,381  ·  6 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x32b84fbe…18d5

0x065c9d…c394

3 touches
1 conflict

0x9308558a…0dda

0x065c9d…c394

3 touches
1 conflict

0x42a7f118…5554

0x065c9d…c394

2 touches
0 conflicts

0x641f4532…f075

0x065c9d…c394

2 touches
0 conflicts

0x7655e120…f5fa

0x065c9d…c394

2 touches
0 conflicts

0x8e67e4fe…e414

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity