← previous blocknext block →recent activity

Analyzing

Block #74,388,627

7 transactions · 6 stateful · 2026-05-13 20:02:56 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,388,627  ·  7 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

0xb9d24e91…9fad

0x065c9d…c394

4 touches
1 conflict

0xbc87525d…6dff

0x065c9d…c394

3 touches
1 conflict

0x44bfa9d8…448e

0x065c9d…c394

2 touches
0 conflicts

0x7b1772b8…f31f

0x065c9d…c394

2 touches
0 conflicts

0x7cec4a19…dda3

0x065c9d…c394

2 touches
0 conflicts

0xbfc05c5c…cbf6

0x065c9d…c394

2 touches
0 conflicts

0xe0cfba04…83b5

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 0x0000000000…00003d

← previous block·next block →recent activity