← previous blocknext block →recent activity

Analyzing

Block #74,281,551

7 transactions · 6 stateful · 2026-05-13 08:10:33 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,281,551  ·  7 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

0xa79e3f0b…7b5e

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x366c7848…6634

0x065c9d…c394

2 touches
0 conflicts

0x7613eaeb…7bb6

0x065c9d…c394

2 touches
0 conflicts

0xe0165b76…6f25

0x065c9d…c394

2 touches
0 conflicts

0xfb096901…3ab4

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

1 conflict on slot 0xa79e3f0b4a…0e7b5e

← previous block·next block →recent activity