← previous blocknext block →recent activity

Analyzing

Block #74,303,481

13 transactions · 9 stateful · 2026-05-13 10:36:35 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,303,481  ·  13 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

0x848626b3…8c3b

0x065c9d…c394

4 touches
1 conflict

0x5ad97c30…dac5

0x065c9d…c394

3 touches
1 conflict

0xa56fb009…edcb

0x065c9d…c394

3 touches
1 conflict

0x000761bd…734d

0x065c9d…c394

2 touches
0 conflicts

0x09b03240…06fb

0x065c9d…c394

2 touches
0 conflicts

0x0c83e950…a8fe

0x065c9d…c394

2 touches
0 conflicts

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x48fdbb87…7be9

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 0x848626b37c…408c3b

← previous block·next block →recent activity