← previous blocknext block →recent activity

Analyzing

Block #74,668,653

13 transactions · 7 stateful · 2026-05-15 03:15:15 UTC

Parallelism

85/100

Blocked

29%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,668,653  ·  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

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x352b1c43…2358

0x065c9d…c394

3 touches
1 conflict

0x2e75864f…b159

0x065c9d…c394

3 touches
1 conflict

0x88c96b08…1b17

0x065c9d…c394

3 touches
1 conflict

0x9dc7d892…62a1

0x065c9d…c394

3 touches
1 conflict

0x765c236f…ff45

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 0xffe431af56…838faa

← previous block·next block →recent activity