← previous blocknext block →recent activity

Analyzing

Block #74,587,816

17 transactions · 14 stateful · 2026-05-14 18:15:20 UTC

Parallelism

88/100

Blocked

7%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,587,816  ·  17 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

0x64cb5b58…2d25

0x065c9d…c394

4 touches
1 conflict

0x50d1d666…b40e

0x065c9d…c394

3 touches
1 conflict

0x5d2960b7…4772

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x252224b4…c96d

0x065c9d…c394

2 touches
0 conflicts

0x2fe2b516…a80b

0x065c9d…c394

2 touches
0 conflicts

0x4f539f05…8377

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 0x64cb5b5803…ab2d25

← previous block·next block →recent activity