← previous blocknext block →recent activity

Analyzing

Block #74,766,687

22 transactions · 18 stateful · 2026-05-15 14:09:51 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.36

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,766,687  ·  22 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

0xf06c2cf5…61bd

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x150af51d…9c42

0x34b655…2a6f

4 touches
1 conflict

0x259f891b…c9fd

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

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

3 conflicts on slot 0xf06c2cf5e4…3161bd

← previous block·next block →recent activity