← previous blocknext block →recent activity

Analyzing

Block #74,234,398

14 transactions · 13 stateful · 2026-05-13 02:57:07 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,234,398  ·  14 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

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xec08de2c…1a04

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xc229a9b8…5250

0x5afd3e…7620

2 touches
0 conflicts

0xdf5c2695…e4cd

0x5afd3e…7620

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

3 conflicts on slot 0xcf3283bab2…c3c9fa

← previous block·next block →recent activity