← previous blocknext block →recent activity

Analyzing

Block #74,462,514

13 transactions · 9 stateful · 2026-05-14 04:14:50 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,462,514  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x889e2c9c…4a19

0x065c9d…c394

3 touches
1 conflict

0x25be5d1c…e978

0x065c9d…c394

3 touches
1 conflict

0x976a3cb1…de12

0x065c9d…c394

2 touches
0 conflicts

0xae5dc57d…0564

0x065c9d…c394

2 touches
0 conflicts

0xcc4abe21…09b6

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

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