← previous blocknext block →recent activity

Analyzing

Block #74,287,150

11 transactions · 9 stateful · 2026-05-13 08:47:45 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,287,150  ·  11 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

0x6db26c98…66f9

0x065c9d…c394

4 touches
1 conflict

0x1dbd9cab…5f9c

0x065c9d…c394

3 touches
1 conflict

0xfc385e6b…8731

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x12216154…8612

0x065c9d…c394

2 touches
0 conflicts

0x3b2ea7fc…bc35

0x065c9d…c394

2 touches
0 conflicts

0x81510ecb…a4af

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x6db26c9877…a266f9

← previous block·next block →recent activity