← previous blocknext block →recent activity

Analyzing

Block #74,555,978

26 transactions · 21 stateful · 2026-05-14 14:41:31 UTC

Parallelism

81/100

Blocked

43%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,555,978  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x801a6e57…d85c

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x5138188e…796b

0x34b655…2a6f

6 touches
3 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0xffedeacf…01f1

0x34b655…2a6f

6 touches
3 conflicts

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0x69017fce…85c1

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

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: 0x34b6552d…112a6f

10 conflicts on slot 0x801a6e5726…c1d85c

← previous block·next block →recent activity