← previous blocknext block →recent activity

Analyzing

Block #74,336,136

9 transactions · 8 stateful · 2026-05-13 14:13:41 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,336,136  ·  9 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

0xc37ee18a…701b

0x065c9d…c394

4 touches
1 conflict

0xdb9d90c4…7ded

0x065c9d…c394

4 touches
1 conflict

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x4d9c31ea…7216

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xa026db14…cb9b

0x065c9d…c394

2 touches
0 conflicts

0xba68d3ba…343d

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

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 0xc37ee18a4f…31701b

← previous block·next block →recent activity