← previous blocknext block →recent activity

Analyzing

Block #74,239,295

8 transactions · 7 stateful · 2026-05-13 03:29:42 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,239,295  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x718f5fc1…b83c

0x065c9d…c394

4 touches
1 conflict

0xcb8940ea…b835

0x065c9d…c394

3 touches
1 conflict

0x1c4a904f…36fa

0x065c9d…c394

2 touches
0 conflicts

0x31881f0b…a5d6

0x065c9d…c394

2 touches
0 conflicts

0x470e6172…9c2a

0x065c9d…c394

2 touches
0 conflicts

0x67e8e552…a195

0x065c9d…c394

2 touches
0 conflicts

0xa51ca39b…7b7b

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