← previous blocknext block →recent activity

Analyzing

Block #74,298,190

8 transactions · 7 stateful · 2026-05-13 10:01:19 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,298,190  ·  8 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

0x088ef45b…af4f

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x412c0dbb…b7ad

0x065c9d…c394

3 touches
1 conflict

0x9bd4d340…5fad

0x065c9d…c394

3 touches
1 conflict

0x3b1d2c2d…c7bb

0x065c9d…c394

2 touches
0 conflicts

0xa316eeaa…eafb

0x065c9d…c394

2 touches
0 conflicts

0xa8ad8016…b042

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

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 0x088ef45bf6…b1af4f

← previous block·next block →recent activity