← previous blocknext block →recent activity

Analyzing

Block #74,247,578

14 transactions · 11 stateful · 2026-05-13 04:24:43 UTC

Parallelism

57/100

Blocked

45%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,247,578  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x0175b7a6…1db9

0x5d823e…89c6

2 touches
0 conflicts

0x0175b7a6…1dbb

0x5d823e…89c6

2 touches
0 conflicts

0x0175b7a6…1dbc

0x5d823e…89c6

2 touches
0 conflicts

0x0ef1e663…8f2a

0x5d823e…89c6

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

10 conflicts on slot 0xcf3283bab2…c3c9fa

← previous block·next block →recent activity